![]() ![]() Such options are mentioned in the man pages of the commands. Note: The -d in commands like “sudo port -d sync” is for activating the debug mode. Use the bellow command, not “sudo port selfupdate” sudo port -d sync ![]() In case you want to erase those environment variables you can use: unset http_proxy HTTP_PROXY Step 3: Sync the port tree over http that make use of your internet connection. Remember to check for these environment variables every time you run your Terminal and are about to use things like port, curl, homebrew, etc. Replace “username”, “password”, “proxyURL” and “portNumber” with their values specifying your proxy settings: export will most probably never work but just in case, add these variable as well… notice that you don’t need rsync:// at the beginning of the value export the bellow command to check the environment variables being used in the current session of the bash shell env Now, type the following at the terminal to export environment variables. Next, escape out of the –insert– mode and save your changes. Scroll to the bottom, enter into –insert– mode and append the following to the list of default specifications Defaults env_keep += "http_proxy HTTP_PROXY ftp_Proxy FTP_PROXY rsync_proxy RSYNC_PROXY" Similar to editing the nf by using the vi editor in bash, edit the sudoer file: sudo visudo Step 2: Keep your proxy related environment variables Then type :x and press ‘return’ to save your changes and return to Terminal. Next, press the ‘esc’ key on your keyboard to exit –insert– mode. rsync:///release/tarballs/ports.tar īellow that line insert this line which will tell Macports to go fetch the daily tarball over http Scroll down to the bottom of file and comment out the following line by typing # in front of it. Once the file is opened in the vi editor press the ‘a’ key on your keyboard to enter into –insert– mode. Use the following code to edit nf using the vi editor in bash sudo vim /opt/local/etc/macports/nf This is because the shell environment doesn’t have the variables specifying your systems proxy settings. “macports::selfupdate base_updated”Įrror: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed Rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) Ĭommand failed: /usr/bin/rsync -rtzv –delete-after rsync:///release/tarballs/base.tar /opt/local/var/macports/sources//release/tarballsĭEBUG: Error synchronizing MacPorts sources: command execution failed Rsync: failed to connect to : Operation timed out (60) > Updating MacPorts base sources using rsync Getting Macports to work over http Step 1: Get the installer from Macports download siteĭownload the latest installation package for your particular OS from: įollow through the prompts after opening it and install Macports but then trying to selfupdate might give this error:ĭEBUG: MacPorts sources location: /opt/local/var/macports/sources//release/tarballs Before I get into the method I assume that you know your proxy settings that may include a username and password for authentication and you have configured you browser to use them. So this blog is about one method that finally worked for me. ![]() Also, many proxy servers aren’t configured to handle rsync. After drudging through numerous forums I finally discovered that sudo command “sanitizes” the shell environment and gets rid of the environment variables concerning proxy settings because of which commands like sudo port -d selfupdateĭon’t work. I ended up struggling for months to get Macports to work and tried every installation method in but nothing worked. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |