Opened 10 years ago
Closed 10 years ago
#44799 closed defect (worksforme)
Error comando v- selfupdate
Reported by: | capn610@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.3.1 |
Keywords: | Cc: | ||
Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Al realizar la actualización de los MacPorts se generó el siguiente error:
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed 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 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]
Change History (2)
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Component: | ports → base |
---|---|
Description: | modified (diff) |
Keywords: | selfupdate removed |
Priority: | High → Normal |
Type: | update → defect |
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Has this ever worked? The usual reason for this error is that your network blocks rsync traffic. Either have your network administrator lift that restriction, or use a different syncing mechanism, such as the http tarball or a Subversion working copy. Selfupdate always uses rsync for updating base, so if you cannot get rsync access on your network, you'll have to use a different method to update base, such as downloading the installer from our web site when we release new versions of MacPorts.