Problems with updating macports

Ken Cunningham ken.cunningham.webuse at gmail.com
Thu Sep 21 19:25:30 UTC 2017


I appears that you couldn't connect to the macports rsync server at one point.

First thing I would do is try again -- perhaps it was something temporary / transient.

If it fails again, then you have to look to see if you're behind a firewall, etc...

Ken

On 2017-09-21, at 9:04 AM, Rino Bandiera wrote:

> DEBUG: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> rsync: failed to connect to rsync.macports.org: No route to host (65)
> rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-45/rsync/clientserver.c(105) [receiver=2.6.9]
> Command failed: /usr/bin/rsync -rtzv --delete-after  rsync://rsync.macports.org/release/tarballs/ports.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> Exit code: 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170921/acaae732/attachment.html>


More information about the macports-users mailing list