#10147 Remove FEDORA-2021-48eb1c8350 which was created in mistake instead of modifying existing one.
Closed: Fixed 2 years ago by mohanboddu. Opened 2 years ago by abbra.

I'd like to delete https://bodhi.fedoraproject.org/updates/FEDORA-2021-48eb1c8350.
I opened it but forgot that we already have a separate bodhi request https://bodhi.fedoraproject.org/updates/FEDORA-2021-234a7eff94

I cannot now update the FEDORA-2021-234a7eff94 with a new build due to FEDORA-2021-48eb1c8350 existence.


Hi, the update is in an unpushed state and should not be propagated anywhere.

I have asked a different question, sorry. Your answer does not address it.

So let me expand a bit. I need to push a new version of FreeIPA to Fedora but I cannot do it now because there is a separate bodhi request that concerns the same package. Regardless whether I have moved a new bodhi request to unpushed state, I cannot add a new build to the other bodhi request. It looks like Bodhi simply cannot handle this and an additional bodhi request has to be removed manually.

So, we used to allow deleting updates. It caused all kinds of chaos... as people would make updates, they would get negative karma/feedback and they would just delete them and make a new one, causing a lot of confusion by testers as to what was tested and what happened. So, a few years ago, bodhi changed to not allow deleting updates ever. Sadly as you see this has a corner case where you want to move a build from one update to another. :(

Alternatives:
Just rebuild the build you need and attach the new one to the right update
find some older build you didn't ever push as an update, attach it to the 'bad' update, then remove the build you need and attach it to the 'good' update.
(since updates not only can't be deleted, you can't remove the last build from them either).

Sorry this is a hassle...

I think we can go with a third option: I was able to push the older update to stable and once it is there, I can push the new update to testing. Would this work from Bodhi point of view?

yep. that would work as well indeed.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

As the alternative works here, I am closing the ticket.

Login to comment on this ticket.

Metadata