RFE: It should be possible to avoid auto-obsolete when delivering a new update

[rwmjones]

People are waiting for this update to get into Fedora 43 because it is required by virt-v2v, see:

https://bodhi.fedoraproject.org/updates/FEDORA-2026-2f0ab803db
https://bugzilla.redhat.com/show_bug.cgi?id=2430487

There is a new version ready for Fedora 43. I'd like to submit an update for it now, but if I do that, it will unnecessarily obsolete the version above (which works fine, it just has a rare build instability which is fixed in the new version).

So now I have to wait another 7 days, then remember to submit an update instead.

It'd be nice if you could tag an update so it didn't auto-obsolete.

[mattiaverga]

I don't think this is possible.
An update being in testing just means that the builds within are tagged in the -updates-testing tag for that release. Pushing another newer build in that same tag will just cause the next compose to include the new build and remove the older one, so having two updates in testing is useless.

But is hould have added "AFAIK" at the start of my comment, perhaps someone else has better knowledge on this topic.