Opened 11 years ago
Closed 11 years ago
#43093 closed defect (worksforme)
Error: Error synchronizing MacPorts sources: command execution failed
Reported by: | kruger@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Dear Macports,
I have a MAC with the latest Maverick installed. I installed Macports according to https://www.ghostwheel.com/merlin/Personal/notes/2013/10/05/macports-on-mavericks/
I think the problem is that I do not know how to do point 8 (Re-install your ports.) after the installation.
When I run: sudo port -v selfupdate
I get the following error:
Gerts-iMac-2:~ gertkruger$ sudo port -v selfupdate Password: ---> 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 /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 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 11 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|---|
Description: | modified (diff) |
comment:2 Changed 11 years ago by mf2k (Frank Schima)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Trac is not for tech support. Follow-up on the Macports Users mailing list instead.
Note: See
TracTickets for help on using
tickets.
For some reason, MacPorts was unable to communicate with our rsync server.
Has this ever worked before?
Some networks restrict access to "unusual" ports, which for some network administrators may include the rsync port. If that's the case for your network, talk to your network administrator about allowing rsync traffic.