On Sat, 22 Nov 2008, Sven Joachim wrote: > On 2008-11-22 18:22 +0100, Raphael Hertzog wrote: > > > The weird thing is that it looks like that only dpkg 1.14.23 > > causes you trouble and not 1.14.22. But the code that deals with > > lonely Triggers-Awaited dates back to Mon Aug 11 (commit > > 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. > > I don't see what changes could explain that the error now gets noticed > > when it wasn't before. And the package that had those fields were not > > recently updated either. > > > > I can certainly get a failure with 1.14.22 if I add Triggers-Awaited > > fields to packages that are marked as installed. So how is it possible > > that you were using dpkg 1.14.22 without troubles yesterday and that now > > you have a borked status file exactly when you upgrade to 1.14.23… > > There is another strange thing in Raj's dpkg log: packages never entered > a state of triggers-awaited or triggers-pending.
Right, Raj, did you configure apt in any strange way? Did you activate the DPkg::NoTriggers option for example? Please check /etc/apt/apt.conf and /etc/apt/apt.conf.d/*. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
