Bug#663167: gconf2: multiarch split means gconf2 trigger may be called when not usable
steve.langasek at canonical.com
Fri Mar 9 01:51:33 UTC 2012
Justification: doesn't upgrade cleanly
We've recently merged your latest multiarch-split gconf2 package into
Ubuntu, and in the process discovered that it was now causing upgrade
failures for users, because the gconf2 trigger was being called while the
libraries were in an inconsistent state.
Since libgconf-2-4 Breaks: libgconf2-4 does not result in dpkg deconfiguring
the reverse-dependencies of libgconf2-4, gconf2 remains configured, and its
trigger can fire if a triggering package is unpacked after (for example)
libgconf-2-4 is unpacked but before gconf-service is unpacked.
The most straightforward fix that I've been able to identify here is for
both of libgconf-2-4 and libgconf2-4 to declare a Breaks: gconf2 (<<
Although this issue doesn't seem to have been reported in Debian yet, as far
as I can tell that's just the luck of the draw, and this bug will eventually
affect some random subset of Debian users as well.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek at ubuntu.com vorlon at debian.org
More information about the pkg-gnome-maintainers