Rebuild for epel9-next kde update
This update has been submitted for testing by tdawson.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
This update includes packages which can't even be build after FEDORA-EPEL-NEXT-2023-1215583109 went to epel9-next stable.
This is completely incompatible update with already published kf5 packages.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update can be pushed to stable now if the maintainer wishes
The problem isn't / wasn't with THIS update, it was with the LAST update. Despite all my testing, there was several packages that snuck in that are uninstallable (and thus preventing building from anything using them).
I can understand - but how to fix situation? Should previous update be pulled back instead?
Can we do that?
If we can unpush to stable, I would love that.
It's not possible to unpush a bodhi update that has gone to stable.
As a last resort, it is possible for releng to manually untag the corresponding koji build to remove the package from the repos. The downside is that leaves us in an inconsistent state where bodhi doesn't match the state of the repo. It is highly preferred to create new update to solve the problem, if possible.
Thank you. I didn't think it was.
As soon as I saw that the 7 packages were uninstallable, I untagged them from epel9-next, that was last week.
I thought downgrading them to the version that these packages were at (22.12) would be best, so they were in this update.
The problem is that bodhi doesn't like that they are at a lower version.
I rebuilt them with their higher version, and saw that they really would install if built with the correct libraries. So I have created a new update with just those 7 packages, here.
Once those make it into -testing I will try again with different tests than I did last time.
Thank you for your effort!
Just so people know, I was doing two types of test installs with the previous update. I tested each packages that it would install individually. I also did the comps groups. And I might have done the "Install every binary at once" test, but I'm not thinking I did.
The main problem was that there was three layers of packages during testing. Those in epel9, epel9-next and epel9-next-testing. epel9-next had about 50 kde packages already that had been rebuilt due to an updated library in CentOS Stream 9.
So when I did my testing of individual packages, some of them picked the epel9-next packages and installed just fine. And when I did my group installs, again, some of them picked the epel9-next packages and installed just fine. But I didn't notice that there was a mis-match of epel9-next and epel9-next-testing.
When the -testing went to stable epel9-next, all of a sudden, those epel9-next packages were gone, because we only keep the latest package in a repo. And thus, those packages that had hard dependencies on the older epel9-next packages, wouldn't install.
Sorry for being long winded. Just throught people would want to know how this happened, and what I'm going to be trying to test against with this (and the other) update.
tdawson edited this update.
Karma has been reset.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2024 Red Hat, Inc. and
bodhi-server 8.0.2^202401201340git30ffe50 on
bodhi is Free Software.
if you have any problems. Read the documentation.