Package: gconf2 Version: 3.2.4-0ubuntu1 Severity: serious Tags: patch Justification: doesn't upgrade cleanly
Hi Joss, 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. https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/948294 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 (<< 3.2.3-2). 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. Cheers, -- 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/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org