Here's the promised info on the binpackage infrastructure: Directories on dipper: (1) /release/weekly/binpackages/${arch} belongs to ${arch} user the build boxes rsync their package caches to here via ssh as ${arch} user (2) /release/binpackages/${arch} belongs to gmirror sign-binpackages.sh syncs files to here from (1), signs them here, makes index (3) /var/tmp/gmirror-releases/releases/${arch}/binpackages belongs to gmirror sync-binpackages.sh syncs files to here from (2) Scripts are on the branch wip/dilfridge of mastermirror-scripts.git and manually tested with "sudo -u gmirror" Estimated disk space: * for any architecture / subarch that builds only stage3, ~250M per directory amd64/17.0/x32 x86/17.0/i686_hardened sparc/17.0/64 ... * for amd64, significantly more, but the corresponding space will be freed in /experimental eventually amd64/17.1/x86-64 5.3 Gbyte TIA for hooking this all up.
PS. sign-binpackages.sh is SLOW and should (as gmirror) at most run once per day sync-binpackages.sh should run (as gmirror) after sign-binpackages.sh has finished.
PPS. The Release Engineering key in /home/gmirror/.gpg-releng did not have any ownertrust set. This made verification of signatures difficult and caused failures in the script. I manually as gmirror set its ownertrust to ultimate and refreshed the trustdb. (Is logical anyway since the secret key is present.) When a new key is generated, this step will have to be included.
dilfridge: as discussed on IRC, the base of this is deployed. Anything else needed?
(In reply to Robin Johnson from comment #3) > dilfridge: as discussed on IRC, the base of this is deployed. > Anything else needed? No, I think we're good. Thank you!
