-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: move a build from unpushed update to another existing update #5485
Comments
Alternatively, having a way to remove all builds attached to an update would also work - that way, we could re-attach the builds to another update. It used to be possible to do that by deleting Bodhi updates, but that functionality was removed a while back. |
I tried that, it did not work. |
@mattiaverga Oh wow, I had no idea that it should work like that - let me give this a try and see if I can merge https://bodhi.fedoraproject.org/updates/FEDORA-2023-b2e6ab4817 into https://bodhi.fedoraproject.org/updates/FEDORA-2023-d422824191 @Conan-Kudo I think you obsoleted the update, but didn't unpush. That may be a crucial difference. |
I did the obsoleting later after I found unpushing didn't work. |
OK, I tried with my two updates and it didn't work either. What I did was first, The web UI errored out with:
I'll just leave them in this state for now if you want to experiment with them in some way. |
Yeah, the commit I linked refers to create a new update with a build from an unpushed update. |
Thanks! |
It would be good to have a way to merge updates together when independent people have accidentally submitted them as separate updates when they do need to land together.
The most recent case of this was with FEDORA-2023-1b4954b53b and FEDORA-2023-a8847a9386, where the former needed to be merged into the latter because they needed to be shipped together.
Unfortunately, there was no way to do it other than for me to do a no-change rebuild, obsolete the old one manually, and add the new build to the correct update.
This was a waste of human and compute resources that could have simply been avoided by having the ability to merge updates.
(Thankfully, this was only wallpapers, but I shudder if we had this problem with chromium or some other time-consuming package.)
The text was updated successfully, but these errors were encountered: