(sorry, no time to look closely at it currently) On Mon, Mar 14, 2011 at 03:15, Steve Langasek <vorlon@debian.org> wrote: > I've noticed what looks like a mismatch between apt's and dpkg's idea of > when a package is configurable, that results in apt asking dpkg to configure > a multi-arch: same package that isn't ready yet, and then bombing out. I fear its related to immediate configuration: Could you try with -o APT::Immediate-Configure=0 ? And, how tries APT to call dpkg exactly? (with/without immediate) -o Debug::pkgDPkgPM=1 Attached is a small testcase for this you can drop in test/integration/ and run it. It should install a same package and tries to dist-upgrade then (in a temp directory of course). The output of the simulations (i have no multiarch-dpkg handy currently) seems to be fine as long as libsame isn't essential (i know, not allowed for a library in real world, but its the easiest way to get the immediate flag). But thinking about it, APT enables auto-deconfiguration: > De-configuring libstdc++6:i386 ... > Unpacking replacement libstdc++6 ... > dpkg: error processing libstdc++6 (--configure): > libstdc++6:amd64 4.5.2-6ubuntu1+multiarch.1 cannot be configured because libstdc++6:i386 is in a different version (4.5.2-5ubuntu3+multiarch.1) Looks for me like libstdc++6:i386 is deconfigured, so the (implicit) Breaks in libstdc++6:amd64 is satisfied and it should be configurable as the configuration would only be forbidden if libstdc++6:i386 would still be configured - but it is deconfigured currently -, doesn't it? Best regards David Kalnischkies
Attachment:
test-multiarch-same
Description: Binary data