Opened 8 years ago
Closed 8 years ago
#51884 closed defect (invalid)
sudo port -v selfupdate not working
Reported by: | vidyapriyadarshini@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.3.4 |
Keywords: | Cc: | khindenburg | |
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Steps :
- After downloading and building port and setting the PATH and MANPATH variables as per instrcutions : run sudo port -v selfupdate
Actual Error :
flipkarts-MacBook-Pro-10:fk-ekl-jarvis vidya.priyadarshini$ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/clientserver.c(105) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 10 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
Change History (2)
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|---|
Description: | modified (diff) |
comment:2 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | khindenburg added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
closing for now - reopen if you still have issues and think it is macports related.
Note: See
TracTickets for help on using
tickets.
Usually this happens when your network blocks rsync traffic. Ask your network administrator. Sometimes, antivirus or security software can block rsync connections; if you use any such software, try disabling it. If you cannot make rsync traffic work on your network, there are alternatives, documented in our wiki, for updating the ports collection using a tarball via http, or using svn.