Re: Ports rsync not working?

[Ryan Carsten Schmidt]

On Dec 3, 2024, at 18:16, Dave Allured wrote:  It looks like the ports tarball is not synchronizing for the past 9 hours or so.  This means that selfupdate is not receiving today's Macports updates.  According to a README in macports-infrastructure, this should be synchronizing every 30 minutes. Well the private server starts mprsyncup every half hour or so, if it is not already running, but these days with 40,000 ports in the collection it can take an hour or more to run.  And the public server syncs from the private server every half hour or so, if a sync is not already running, but how long a sync takes depends on how much data needs to be transferred.  Am I misinterpreting, or is something broken? Try again? According to Mirror-Status ftp.fau.de (ftp.uni-erlangen.de) ftp.fau.de The most recent sync from the private server to the public one took 7 hours 48 minutes to complete. Most other recent syncs complete in less than an hour. The most likely reason for this outlier is if large files (archives and/or distfiles) had to be transferred, for example if a large port was updated.