Hi SIGs folks (and testing community) !
Just to inform you that next Monday (May 15th) , we'll migrate our sign-and-push process to a different infra/machine, but you shouldn't see any service disruption.
We'll also implement signing for the packages tagged to -testing, and so landing on https://buildlogs.centos.org. It's a request that came through the Infra tracker (https://pagure.io/centos-infra/issue/1131) and that was approved by the CentOS Project board (all details in that ticket)
There is nothing to do at your side (it's not an opt-in scenario, it will be implemented for all SIGs), as it will be transparently processed next time you'll (un)tag-build a package (or more) to your -testing tags. (We can also manually process existing -testing repositories on demand , should there be a need/request)
You can though bump your 'release' pkg (that contains the .repo files) to reflect gpgcheck=1 and point to same key as for repositories going to the mirror network, but that's optional (SIG's choice)
I'll also update the SIG Guide (https://sigs.centos.org/guide/delivery/) to reflect that change.
Kind Regards,
On 11/05/2023 08:44, Fabian Arrotin wrote:
Hi SIGs folks (and testing community) !
Just to inform you that next Monday (May 15th) , we'll migrate our sign-and-push process to a different infra/machine, but you shouldn't see any service disruption.
We'll also implement signing for the packages tagged to -testing, and so landing on https://buildlogs.centos.org. It's a request that came through the Infra tracker (https://pagure.io/centos-infra/issue/1131) and that was approved by the CentOS Project board (all details in that ticket)
There is nothing to do at your side (it's not an opt-in scenario, it will be implemented for all SIGs), as it will be transparently processed next time you'll (un)tag-build a package (or more) to your -testing tags. (We can also manually process existing -testing repositories on demand , should there be a need/request)
You can though bump your 'release' pkg (that contains the .repo files) to reflect gpgcheck=1 and point to same key as for repositories going to the mirror network, but that's optional (SIG's choice)
I'll also update the SIG Guide (https://sigs.centos.org/guide/delivery/) to reflect that change.
Kind Regards,
Just to let you know that it's now "live" and realizing that some SIGs (like automotive SIG) were building but never promoting to -release tags their kernel-automotive package (https://cbs.centos.org/koji/packageinfo?packageID=8886), so suddenly the signing process has to process them all .. That can explain why you'll see (today only) some "lag" between your tag-build operation and then the distRepo task being launched on cbs (and then after packages going out)
-
Fabian Arrotin