Opened 4 years ago

Closed 4 years ago

#52569 closed defect (worksforme)

port -v selfupdate fails

Reported by: herminio.hernandezjr@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: server/hosting Version: 2.3.4
Keywords: Cc: ryandesign (Ryan Schmidt)


I installed macports on a PowerMac G5 running 10.5.8. When I try to update the ports tree I get this:

herminio-hernandezs-power-mac-g5:~ herminiohernandez$ sudo port -dv selfupdate
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/
--->  Updating MacPorts base sources using rsync

Willkommen auf dem RSYNC-server auf
Nicht all unsere Mirror sind per rsync verfuegbar.

Welcome to the RSYNC daemon on
Not all of our mirrors are available through rsync.

receiving file list ... rsync: link_stat "/tarballs/base.tar" (in release) failed: No such file or directory (2)

sent 4 bytes  received 9 bytes  5.20 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-35.2/rsync/main.c(1400) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync:// /opt/local/var/macports/sources/
Exit code: 23
DEBUG: Error synchronizing MacPorts sources: command execution failed
    while executing
"macports::selfupdate [array get global_options] base_updated"
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

What am I missing?

Change History (2)

comment:1 Changed 4 years ago by herminio.hernandezjr@…

Here is an update. I rebooted the G5 and ran sudo port -v sync and my database is now synced.

comment:2 Changed 4 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Component: portsserver/hosting
Keywords: selfupdate rsync removed
Resolution: worksforme
Status: newclosed

Maybe the server was temporarily in a weird state. I am in the process of rewriting the scripts that generate those tarballs, so hopefully in future you won't see problems like that. If you see that problem again, wait an hour and try again.

Note: See TracTickets for help on using tickets.