Possible to submit an update without obsoleting?

[Richard W.M. Jones]

In general I like the auto-obsoleting feature in Bodhi, but is there a
way to disable it for a particular update?

The reason is that I've got libguestfs-1.10.1-1.fc15 waiting to go
into stable.  I've also just built libguestfs-1.10.2-1.fc15 which is a
further update along the upstream stable branch.

If I submit this second update, it will auto-obsolete the first
update.  However the first update is perfectly fine in itself, and
more importantly it fixes a dependency problem.  If it gets obsoleted
then users will have to wait another 3-4 days in order to get the
dependency fix and won't be able to use the package at all during this
time.  My only choice seems to be to not submit the second update at
all, which means no one can test it, and the eventual release of it
will be later than it needs to be.  I'd like to "pipeline" the
updates.

This is a general problem with auto-obsoleting if the period between
releases < the period in updates-testing (which is the case in
libguestfs because of our quite rapid release schedule).  In the past
I've had chains of updates causing delays to get *any* package out of
3-4 weeks.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/