Opened 8 years ago
Last modified 8 years ago
#52629 closed defect
MacPorts sync failed — at Version 1
Reported by: | Behinder (behinder) | Owned by: | admin@… |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | server/hosting | Version: | 2.3.4 |
Keywords: | Cc: | ryandesign@… | |
Port: |
Description (last modified by raimue (Rainer Müller))
Hello. yesterday everything was OK. Today I wanted to sync my port tree and the result is:
Willkommen auf dem RSYNC-server auf ftp.fau.de. Nicht all unsere Mirror sind per rsync verfuegbar. Welcome to the RSYNC daemon on ftp.fau.de. 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) done sent 4 bytes received 9 bytes 26.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [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: 23 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
Change History (1)
comment:1 Changed 8 years ago by raimue (Rainer Müller)
Cc: | ryandesign@… added |
---|---|
Component: | ports → server/hosting |
Description: | modified (diff) |
Keywords: | rsync sync removed |
Owner: | changed from macports-tickets@… to admin@… |
Note: See
TracTickets for help on using
tickets.
Please remember to use WikiFormatting.
There was a similar report on IRC. The reporter noted it was working again quickly afterwards. I could not see the failure condition myself, as the tarball existed when I checked. Looks like some temporary glitch happened, maybe the mirror was updated at the same time?