On Thu, Mar 21, 2013 at 22:56:49 +0100, Julian Andres Klode wrote: > On Thu, Mar 21, 2013 at 10:28:01PM +0100, Julien Cristau wrote: > > On Thu, Mar 21, 2013 at 22:21:29 +0100, Michael Biebl wrote: > > > > > That said, I can no longer really contribute to this bug as I'm not able > > > to reproduce. Anyone experiencing this problem should probably make a > > > copy of /var/lib/dpkg/status so we/David can have a look. > > > > > Yeah, I made one IIRC, just don't have it right now. I'm kind of afraid > > we won't manage to fix all the possible cases where this happens, > > though, and will need to explain in the release notes how to work around > > it if people still face this error message. If anyone has ideas on how > > to write that, I'd be happy to see your suggestions :) > > You mean something like: > If apt-get tells you that it "could not perform immediate configuration" > on something, re-run it with -o APT::Immediate-Configure=0 > ? > What's the downside of that configuration option? Should we recommend to always do that for squeeze to wheezy upgrades? The text in apt.conf(5) isn't overly encouraging. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature