On 2008-06-24 21:44 +0200, Sven Joachim wrote: > On 2008-06-24 17:58 +0200, Jordi Mallach wrote: > >> As promised, here is my dpkg.log. > > Thanks. I'll analyse it a bit: > > ,---- > | 2008-06-23 10:50:36 startup archives unpack > | 2008-06-23 10:50:49 upgrade dpkg 1.14.19 1.14.20 > | 2008-06-23 10:50:49 status half-configured dpkg 1.14.19 > | 2008-06-23 10:50:49 status unpacked dpkg 1.14.19 > | 2008-06-23 10:50:49 status half-installed dpkg 1.14.19 > | 2008-06-23 10:50:50 status triggers-pending man-db 2.5.2-1 > | 2008-06-23 10:50:51 status half-installed dpkg 1.14.19 > | 2008-06-23 10:50:51 status half-installed dpkg 1.14.19 > | 2008-06-23 10:50:51 status unpacked dpkg 1.14.20 > | 2008-06-23 10:50:51 status unpacked dpkg 1.14.20 > | 2008-06-23 10:50:52 trigproc man-db 2.5.2-1 2.5.2-1 > | 2008-06-23 10:50:52 status half-configured man-db 2.5.2-1 > | 2008-06-23 10:50:53 status installed man-db 2.5.2-1 > | 2008-06-23 10:51:03 startup packages configure > | 2008-06-23 10:51:03 configure dpkg 1.14.20 1.14.19 > | 2008-06-23 10:51:03 status unpacked dpkg 1.14.20 > | 2008-06-23 10:51:03 status unpacked dpkg 1.14.20 > | 2008-06-23 10:51:03 status unpacked dpkg 1.14.20 > | 2008-06-23 10:51:03 status unpacked dpkg 1.14.20 > | 2008-06-23 10:51:03 status unpacked dpkg 1.14.20 > | 2008-06-23 10:51:03 status half-configured dpkg 1.14.20 > | 2008-06-23 10:51:03 status triggers-awaited dpkg 1.14.20 > `---- > > This is the failed installation. Note that man-db is in state installed > after it, which is because its postinst always exits successfully > when triggered. I'm not sure that this is TRT, but that's how it is. > > But that's not the whole story. Despite all the man-db error messages, > the trigger processing ended successfully, which means that dpkg should > have gone back to status unpacked.
I should have read more carefully. Indeed it goes back to unpacked and the postinst is run, but then the status is set back to triggers-awaited. Compare that with the log from my upgrade: ,---- | 2008-06-19 07:07:13 startup archives unpack | 2008-06-19 07:07:14 upgrade dpkg 1.14.19 1.14.20 | 2008-06-19 07:07:14 status half-configured dpkg 1.14.19 | 2008-06-19 07:07:14 status unpacked dpkg 1.14.19 | 2008-06-19 07:07:14 status half-installed dpkg 1.14.19 | 2008-06-19 07:07:14 status triggers-pending man-db 2.5.2-1 | 2008-06-19 07:07:14 status half-installed dpkg 1.14.19 | 2008-06-19 07:07:15 status half-installed dpkg 1.14.19 | 2008-06-19 07:07:15 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:15 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:15 trigproc man-db 2.5.2-1 2.5.2-1 | 2008-06-19 07:07:15 status half-configured man-db 2.5.2-1 | 2008-06-19 07:07:16 status installed man-db 2.5.2-1 | 2008-06-19 07:07:19 startup packages configure | 2008-06-19 07:07:19 configure dpkg 1.14.20 1.14.20 | 2008-06-19 07:07:19 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:20 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:20 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:20 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:20 status unpacked dpkg 1.14.20 | 2008-06-19 07:07:20 status half-configured dpkg 1.14.20 | 2008-06-19 07:07:20 status installed dpkg 1.14.20 `---- Apart from the time stamps, the only difference is the last line, where things went wrong for you. The status should have changed to "installed" or "failed-config" depending on the outcome of the postinst, but not to "triggers-awaited". To the dpkg developers: should not have been the state of dpkg "triggers-awaited" somewhere earlier in the installation process, namely when the triggers are actually processed? Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
