website problem

Lars Sonchocky-Helldorf lars.sonchocky-helldorf at
Fri Sep 4 14:21:31 PDT 2015

Meanwhile, the rest of the macport servers are now down too …

I get this when trying to selfupdate:

localhost:~ lars$ sudo port -v selfupdate
--->  Updating MacPorts base sources using rsync
rsync: getaddrinfo: 873: nodename nor servname provided, or not known
rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-40/rsync/clientserver.c(105) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync:// /opt/local/var/macports/sources/
Exit code: 10
Error: Error synchronizing MacPorts sources: command execution failed
To report a bug, follow the instructions in the guide:
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
localhost:~ lars$ 

Am 30.08.2015 um 01:24 schrieb Ryan Schmidt:

> has been down for a few days. We have reported the problem to the Mac OS Forge administrator and are awaiting a reply from him. Until it's back up, please feel free to report problems here on this mailing list. Gideon, other ways of looking up a port include the "port search" function on the command line; the database at ; and the Subversion repository which you can access via a Subversion client (including the command line "svn" program) at .
>> On Aug 29, 2015, at 10:32 AM, Tim Johnson <tim at> wrote:
>> Same problem here (Alaska)
>> Times out at 
>> (same as with earlier)
>> from my server in Provo Utah, times out at
>> * Gideon Simpson <gideon.simpson at> [150829 07:23]:
>>> I’m trying to look up a port and I get an error when navigating to any of the <> pages.
>>> -gideon
> _______________________________________________
> macports-users mailing list
> macports-users at

More information about the macports-users mailing list