Bug#697025: gstreamer0.10: please re-upload built against GLib 2.32

[Simon McVittie]

On 09/01/13 21:54, Michael Biebl wrote:
> On 09.01.2013 22:29, Simon McVittie wrote:
>> As far as I can work out, bumping libgstreamer0.10-0's shlibs
>> would only help to achieve this if we additionally NMU a bunch of
>> packages to rebuild them against the new libgstreamer0.10-0 so
>> they get a dependency.
> 
> How many would need a sourceful upload?

See <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694525#59>.
tl;dr: up to 22 sourceful and 38 binNMU, although not all of those
depend on GStreamer (some depend directly on GLib).

Having said that, if Julien's reasoning from
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674156#54> is valid
for Gst, then it's presumably valid for GLib as well? If so, then the
thing to do would be to bump GLib's shlibs instead of adding the
Breaks, and sourceful-upload or binNMU those 60 packages (as appropriate).

> I'm worried that adding new Breaks to libglib2.0-0 might bring
> back those problems.

Yeah, I was getting worried about that too.

The way I see this is that there are some sets of packages in wheezy
that are already in a broken situation. By making a sourceful upload
of gstreamer0.10, together with the sourceful upload of swami that has
already happened and a pile of 14 binNMUs (see 694525#59), we can get
full upgrades into a consistent state. I agree that "full upgrades
work" is less desirable than "every partial upgrade allowed by apt
works" - but it's also better than the situation we're in right now!
In particular, I believe that after those uploads, gnome-dvb-daemon,
the package that started all this, would be able to build on the
affected architectures again.

I've spent some time trying to gather and provide useful information,
but I do not maintain the packages in question, and I am unlikely to
be able to do 22 sourceful uploads of unfamiliar packages any time
soon. Better plans gratefully received. If you (for broad plural
values of "you") would like me to leave this discussion and let the
maintainers of the affected packages sort it out among themselves,
please say.

    S