On Sat, 22 Nov 2008, Raj Kiran Grandhi wrote: > Just did that but still dpkg complains of the same problem albeit for a > different package (libhtml-format-perl this time), so I do not think it > is a problem with one specific mis-behaving package. > > Will it be too invasive if I remove all the 34 "Triggers-Awaited" lines?
No, it's fine. > What files should I backup before doing this? None. 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… Did you do anything special recently that could have an impact on the status of all those packages ? Can you check if you already had all those Triggers-Awaited tags in the previous days ? Check in the backups: /var/backups/dpkg.status.* Maybe send us the one that corresponds to Nov 20th. 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]
