Changes between Initial Version and Version 1 of Ticket #44799


Ignore:
Timestamp:
Aug 28, 2014, 2:44:22 AM (10 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #44799

    • Property Keywords selfupdate removed
    • Property Component changed from ports to base
    • Property Type changed from update to defect
    • Property Priority changed from High to Normal

  • Ticket #44799 – Description

    initial v1  
    11Al realizar la actualización de los MacPorts se generó el siguiente error:
     2{{{
    23Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
    34
    … …  
    67rsync: failed to connect to rsync.macports.org: Operation timed out (60)
    78rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]
     9}}}