base.tar not updating on rsync

[jmroot (Joshua Root)]

It doesn't seem to be just a matter of everything needing more time to sync. Currently:

% rsync --no-motd rsync://rsync.macports.org/release/base/config/                
drwxr-xr-x          4,096 2024/04/02 13:59:52 .
-rw-r--r--            423 2021/05/19 19:57:57 README.TXT
-rw-r--r--             62 2024/01/24 23:32:21 RELEASE_URL
-rw-r--r--              6 2017/08/23 07:10:39 dp_version
-rw-r--r--              6 2024/04/02 13:59:52 macports_version
-rw-r--r--              6 2017/08/23 07:10:39 mp_version
% rsync --no-motd rsync://rsync.macports.org/release/tarballs/             
drwxr-xr-x          4,096 2024/04/03 09:27:41 .
-rw-r--r--    114,414,592 2024/02/01 12:35:48 base.tar
-rw-r--r--            512 2024/02/01 12:35:49 base.tar.rmd160
-rw-r--r--    126,614,016 2024/04/03 09:27:28 ports.tar
-rw-r--r--            512 2024/04/03 09:27:32 ports.tar.rmd160
drwxr-xr-x          4,096 2024/04/03 09:27:42 PortIndex_darwin_10_i386
…

[ryandesign (Ryan Carsten Schmidt)]

The servers were offline for awhile after a circuit breaker tripped. It looks like mprsyncup was in progress when the power went out. It had already updated the local git clone of base to the tag specified in RELEASE_URL, determined that this changed the git clone due to the 2.9.2 release, and was in the process of rsyncing the changes to another directory, after which it would have created the new base.tar. When mprsyncup ran again after power came back on, it determined that updating the git clone to the RELEASE_URL tag did not change it so it did not proceed to rsync or make the tarball.

To fix this, I ran sudo -u buildbot git checkout v2.9.1 in the git clone so that on the next mprsyncup run it should again notice a change and update the tarball. I'll keep an eye on it.

[ryandesign (Ryan Carsten Schmidt)]

It's been updated.

[jmroot (Joshua Root)]

Thanks Ryan.