9/3/2023 0 Comments Macports rsyncI used the binary installer to install darwinports/macports but it did not create any of the directories required to install Tsocks. I'll check what happens on the next sync.I am having trouble installing Darwinports/Macports and Tsocks on my Snow Leopard. I'll take the opportunity to update and reboot the router before starting builds again.Ī sync was happening now, and it transferred many R packages before failing with rsync: writer error: Broken pipe (32). Most buildbot builds have been paused due to a tornado watch but that seems to be done now. Or maybe it just returns an error, and maybe FAU is running a script that retries a number of times if it gets that specific error. There might be a limit to the number of retries. Maybe it retries automatically to get the new files. I'm not sure how rsync handles that situation. Maybe the difference is that with clang, we spend several hours building each port during which time an rsync run could complete without any files having changed on the server, whereas now we're building many small ports and between the time an rsync run starts and the time it finishes new files have appeared on the packages server. when several clang ports are updated, so I'm not sure why this would be a problem now. It's not unusual for the builders to be busy for days at a time, e.g. We have been building ~2000 R ports on each builder, in small batches, since about the time this issue started. (All other mirrors sync from FAU.) Or perhaps all of the traffic from FAU is what was causing other services to disconnect. It's possible that FAU is experiencing similar unexpected network disconnections when trying to rsync from the main server. We've had multiple occasions in the past couple days when the off-site Apple Silicon builder has unexpectedly lost the connection to the master, and I've also noticed some network issues on my machine on the same network. Nothing was changed in my local config, and same problem happens on three machines (10.6.8 Rosetta, 10.6 PPC, 10.4.11). There are obviously much more ports updated in reality, but they do not get updated. There is no specific error, they just do not sync with remote ones. Data is downloaded, sync does not happen: old ports are still there. What problem I face now is that ports do not get actually synced at all from Macports servers. Yes, of course there is no 10.6 ppc index. MacPorts should generate or update the PortIndex locally. There never has been and never will be a file PortIndex_darwin_10_powerpc on the server because Apple never released that OS for that processor.įailure to get a PortIndex from the server should not be a problem. Same problem on 10.6 PPC, so it is not a specific machine issue. Rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-40/rsync/main.c(1400) Ĭommand failed: /usr/bin/rsync -rtzvl -delete-after -include=/PortIndex.rmd160 -include=/PortIndex -exclude=* rsync:///macports/release/tarballs/PortIndex_darwin_10_powerpc/ /opt/local/var/macports/sources//macports/release/tarballsĬreating port index in /opt/local/var/macports/sources//macports/release/tarballs/ports Sent 50 bytes received 9 bytes 23.60 bytes/sec rsync: change_dir "/release/tarballs/PortIndex_darwin_10_powerpc" (in macports) failed: No such file or directory (2) Not all of our mirrors are available through rsync. Nicht all unsere Mirror sind per rsync verfuegbar. Synchronizing local ports tree from rsync:///macports/release/tarballs/ports.tar
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |