Bug#674156: glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips

Simon McVittie smcv at debian.org
Mon Jan 28 09:38:47 UTC 2013


On Fri, 11 Jan 2013 at 18:39:24 +0000, Simon McVittie wrote:
> 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.

Julien has NMU'd gstreamer0.10 and scheduled some binNMUs, and swami has
migrated, so all we're waiting for to achieve this is for gstreamer0.10
to migrate. (This can be tracked by waiting for #697025, which is also RC,
to migrate.)

So, assuming no serious problems with the NMU, it's only a matter of time
before full upgrades are OK.

Regarding the original bug, gnome-dvb-daemon was recently built on the
affected architectures; it is now built on all Linux architectures.
So, from that point of view, job done.

As for partial upgrades: Julien's NMU of gstreamer0.10 bumped the shlibs,
so if dependent packages are rebuilt (up to 22 source NMUs of Multi-arch: same
packages, and up to 38 binNMUs of other packages,
see http://bugs.debian.org/694525#59), certain broken combinations
(namely: new dependent package, old gstreamer0.10) will be prevented.
There hasn't been any systematic upload of these; it's an open question
whether it's worthwhile to do all of these, or just the binNMUs, or neither.

The other broken combination (new gstreamer0.10, old dependent package)
can only be addressed via Breaks relations. I think Julien's conclusion
was that this has an unacceptable risk of introducing weird upgrade bugs
where apt fails to find a solution, similar to
<http://bugs.debian.org/676485>?

Regards,
    S



More information about the pkg-gnome-maintainers mailing list