[MacPorts] #48946: Selfupdate fails
MacPorts
noreply at macports.org
Tue Sep 22 10:21:22 PDT 2015
#48946: Selfupdate fails
---------------------------+--------------------------------
Reporter: kevin.lemm@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.3.3
Resolution: | Keywords:
Port: |
---------------------------+--------------------------------
Changes (by ryandesign@…):
* component: ports => base
Old description:
> sudo port -v selfupdate
> ---> 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
>
> When checking https://rsync.macports.org/releases I see an 404 Not found
> message. Has this folder been moved or renamed?
> We are not blocking any related ports on our network and there is no
> firewall installed on the system.
New description:
{{{
sudo port -v selfupdate
---> 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
}}}
When checking https://rsync.macports.org/releases I see an 404 Not found
message. Has this folder been moved or renamed?
We are not blocking any related ports on our network and there is no
firewall installed on the system.
--
Comment:
> {{{
> rsync: failed to connect to rsync.macports.org: Connection refused (61)
> }}}
It works fine for me. Maybe there was a temporary server problem? We did
have a brief outage on our Trac server earlier today; not sure what
happened or if the rsync server was also impacted.
> When checking https://rsync.macports.org/releases I see an 404 Not found
message. Has this folder been moved or renamed?
That 404 response is normal, because that is not a valid URL.
rsync.macports.org is not meant to be used as an http(s) server; it is
meant to be used as an rsync server.
--
Ticket URL: <https://trac.macports.org/ticket/48946#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list