Opened 11 years ago
Closed 11 years ago
#43409 closed defect (invalid)
Unable to selfupdate after installation
Reported by: | crackerhugo@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi,
I follow the step to step installation guide at end I had the following issue:
---> Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Connection refused (61) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/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 Error: Follow http://guide.macports.org/#project.tickets to report a bug
Change History (3)
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|---|
Description: | modified (diff) |
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
See also wiki:FAQ#selfupdatefails
comment:3 Changed 11 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Has this ever worked? MacPorts uses rsync for selfupdate; some networks block rsync access. Talk to your network administrator about allowing rsync access. If that's not possible, other syncing methods are discussed in the guide (tarball; svn).