Learn more about these different git repos.
Other Git URLs
selinux-policy-36.8-1.fc36 was pushed in stable updates as FEDORA-2022-47789bbc9d on 2022-05-02. It didn't make it into the base repo, there's selinux-policy-36.7-1.fc36 (repo). But it should've been in the stable updates repo, and it's not there either (repo).
selinux-policy-36.8-1.fc36
selinux-policy-36.7-1.fc36
We received a failed upgrade bugreport because of this, see rhbz 2084401.
I have no idea why that system wants to download selinux-policy-36.8-1.fc36 when it is not referred by base+updates repos metadata. And why packagekit wants to download it from the base repo. The package is now accessible in updates-testing only.
I guess this situation could occur if selinux-policy-36.8-1.fc36 was accessible in stable updates for some time, but now it isn't. Perhaps some repo blip occurred and it reverted to an earlier state, or lost a package, I don't know. But it's the only explanation I have why that system could try to download something that's no longer available.
So, we need to push selinux-policy-36.8-1.fc36 to stable updates where it should be. Can you please make sure this happens, somehow? Hopefully it will fix these upgrade issues (and it also fixes a lot of other issues which should have been solved for our users by now). Thanks!
When do you need this? (YYYY/MM/DD) Immediately
If we cannot complete your request, what is the impact? Broken upgrades, missing SELinux fixes
CC @adamwill
So the reason why this happened is that I did move the release in mirrormanager from development/36 to release/36, and the development had last nightly compose with 36.8-1 and releases/36 has the actual compose with 36.7-1
I am trying to get it into the updates compose.
@humaton Can you please look whether it affected any other packages as well?
@kparal potentially some of the push requests from this ticket https://pagure.io/releng/issue/10670
So I was looking into how to fix this and the least hackish way I came up with is to bump to selinux-policy-36.8-2.fc36 and submit bodhi update.
Metadata Update from @phsmoura: - Issue tagged with: high-gain, high-trouble, ops
selinux-policy should be the only thing affected as it was the only case where we had the problem of the older build going into the RC due to it being in the override repo. I think we checked all the others and verified they didn't have that issue.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-034d8cc9d9 was pushed stable and it's present in the master repo, so let's hope this is fixed.
Metadata Update from @kparal: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.