Let's uncomment the global `min_karma` and
`critpath.mandatory_days_in_testing` values to make it clearer
that those are our values. At present we wind up using Bodhi's
built-in defaults for these, which are the same, but it's not
really clear and there's no inherent reason why we *ought* to
rely on Bodhi's defaults rather than stating our own here.
Also, per the update policy, critpath updates should be allowed
to go stable after 3 days between u-t activation and Beta freeze,
just the same as non-critpath. See
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#critpath-updates
Signed-off-by: Adam Williamson <awilliam@redhat.com>
- disable nightly compose cron job
- disable mandatory_days_in_testing override
- revert bugzilla exclusion
- add epel10.0 to new-updates-sync
When this is merged, we'll also need to change the following settings in
the EPEL-10.0 bodhi release:
- state: current
- composed-by-bodhi: true
- create-automatic-updates: false
https://pagure.io/epel/issue/300
Signed-off-by: Carl George <carlwgeorge@gmail.com>
EPEL-10.0 needs an override to use 10 in the repomd URL instead of 10.0.
We'll need to move this forward over time to stay on the leading minor
version, allowing trailing minor versions to use the default repomd URL.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
We had the syntax wrong here, it's space seperated, not ,
so the entire thing was getting checked and of course failing.
Lets try again now with space seperator
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
bodhi is failing to finish a f40-updates-testing push because it's
looking for the ppc64le repomd on the primary location instead of the
secondary one.
This should fix it, but I don't understand how it worked before.
Did we just get lucky and always check aarch64 before anything else?
I can't see anything that changed in config around this off hand. ;(
Will try this and see if it fixes it for now...
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This removes the different definitions of `sent_topics` for Bodhi, which
were causing issue https://pagure.io/releng/issue/11827
It also brings the bodhi options in the `os_control*` group vars into
the same vars file.
Signed-off-by: Aurélien Bompard <aurelien@bompard.org>
bodhi was using a small script to copy flatpak images from candidate
registry to registry. This was done because skopeo wasn't able to copy
multi-arch containers at the time. It has since gained the ability to do
that and we should stop using the temporary script to do this.
The script doesn't understand the new f39+ flatpaks hash passed to it so
it fails to push them.
This patch switches bodhi to use normal skopeo and pass it -a which
should tell it to copy all the arches, not just the one it's running on.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
