On Sat, 2005-03-12 at 02:03 -0800, Steve Langasek wrote: > Is it certain that this is a dpkg bug? I notice that the submitter's > typescript shows he was using apt 0.5.27 when upgrading, which was before > the Dpkg::MaxArgs setting was bumped to 1024 -- the first typescript shows a > total of 640 packages being upgraded, and the second typescript shows 281 > packages not fully installed or removed, so perhaps this is a bad dpkg > invocation, not a bug in dpkg itself? > I don't think it's an apt issue, both emacsen-common and a2ps were passed to dpkg in the same run (they were unpacked within the same block) -- I need to digest the typescripts a little more, but I'm tending towards that it is a dpkg bug. Not in the least because I have a hunch I've seen something similar myself since a change was made to the depcycle breaker last year. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part