Opened 9 years ago
Closed 9 years ago
#47018 closed defect (worksforme)
selfupdate failed
| Reported by: | dmytro.semenets@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | ||
| Port: |
Description
port selfupdate failed wilt message:
Mac-mini:~$ sudo port -v selfupdate
Password:
---> 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
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 9 years ago by dmytro.semenets@…
| Cc: | dmytro.semenets@… added |
|---|
comment:2 Changed 9 years ago by neverpanic (Clemens Lang)
| Cc: | dmytro.semenets@… removed |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
You don't need to Cc yourself.
See wiki:FAQ#selfupdatefails. Since the server works fine for me, I'm assuming the problem is with the network on your end. Does your corporation/organization block outbound access to rsync? Basically, see the FAQ and links from there, it should explain what to test and how to work around potential problems.
Note: See
TracTickets for help on using
tickets.
Cc Me!