Raphael Hertzog wrote:
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.
Done. Removed all the Triggers-Awaited lines and now dpkg is happy :)
Thank you.
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…
I think I faced this problem even with 1.14.22. I had attempted a
dist-upgrade several days back. dpkg was one of the packages marked for
upgrade and it crashed after being unpackd (I think). I did not pay much
attention to the specific error message then. I had the older
dpkg-1.14.22 deb lying around in /var/cache/apt/archives and I manually
unpacked it into a temporary directory can copied over the dpkg
executable to /usr/bin. So, the actual executable I had been using
earlier was 1.14.21.
Sorry for the confusion.
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.*
Yes, all the backups have Triggers-Awaited tags. But, as I mentioned
earlier, dpkg 1.14.21 was apparently ok with that.
Maybe send us the one that corresponds to Nov 20th.
Cheers,
--
If you can't explain it simply, you don't understand it well enough.
-- Albert Einstein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
