On Mon, Mar 14, 2011 at 08:49:04PM -0700, Steve Langasek wrote:
> > 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
> Yes, I agree that this is pro
On Mon, Mar 14, 2011 at 12:10:35PM +0100, David Kalnischkies wrote:
> (sorry, no time to look closely at it currently)
Don't worry :)
> On Mon, Mar 14, 2011 at 03:15, Steve Langasek wrote:
> > I've noticed what looks like a mismatch between apt's and dpkg's idea of
> > when a package is configur
(sorry, no time to look closely at it currently)
On Mon, Mar 14, 2011 at 03:15, Steve Langasek 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 r
Package: apt
Version: 0.8.12
Severity: important
User: vor...@debian.org
Usertags: multiarch
Hi again :)
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 read
4 matches
Mail list logo
