(breaking my promise, but as it is marked as a release-blocker now) On Thu, Mar 21, 2013 at 8:09 PM, Julien Cristau <jcris...@debian.org> wrote: > On Thu, Mar 21, 2013 at 19:59:58 +0100, Michael Biebl wrote: >> Fwiw, I can no longer reproduce this myself. >> I've done some recent test dist-upgrades from a default squeeze GNOME >> installation to wheezy, which worked fine. >> >> From my POV, this bug can be closed. >> > From mine it can't, because I've upgraded a machine last week and had > a similar failure (except with some java stuff instead of gstreamer).
Pictures^Wdpkg-status files or it didn't happen, as I said multiple times now. The problem is that there is no "this bug" as this message is kinda catch-all, so its extremely likely that different bugs in APT (and in dependency chains) result in the very same message. Even more so if the message is completely different (and yes, a different package makes it completely different). There is no workaround beside the config option the message mentions and there is also no such thing as a fix we could backport. I also want to mention that there wasn't a lot of change in this code between lenny and squeeze - beside some cornercases, debug enhancements and *drum roll* changing the string of the message to the current form from "Internal error, could not immediate configure %s". So I wonder a bit what changed in how we write down dependencies after lenny vs. after squeeze as this wasn't such a popular error condition before … (I especially wonder how all these packages manage to become pseudo-essential) I am already scared what will creep up for jessie, now that we had a lot of code changes in that area in apt/wheezy. It will be so much fun … not. So it would be interesting to know about which versions we are talking here. The original bugreport e.g. is against an early post-squeeze APT version, so are other instances now against apt/squeeze or against apt/wheezy or some version in-between? Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
