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. Instead the installation ended abruptly with "E: Sub-process /usr/bin/dpkg exited unexpectedly". This may be due to the the lack of disk space in /var, but in any case dpkg should have left an error message. The resulting state of packages after the unexpected exit looks really inconsistent. ,---- | 2008-06-23 11:09:02 startup packages configure | 2008-06-23 11:09:15 startup packages configure | 2008-06-23 11:09:28 startup packages configure | 2008-06-23 11:10:09 startup packages configure | 2008-06-23 11:10:29 startup packages configure | 2008-06-23 11:10:42 startup packages configure | 2008-06-23 11:13:48 startup packages triggers-only | 2008-06-23 11:13:57 startup packages configure | 2008-06-23 11:19:21 startup packages configure | 2008-06-23 11:19:22 startup packages configure | 2008-06-23 11:24:00 startup packages configure `---- These look like attempts to configure dpkg, as if you had run "dpkg --configure --pending". As you said, dpkg did not allow that. But if it did, the triggers would _not_ have been processed correctly anyway, the only way for that is to reinstall the triggering package. ,---- | 2008-06-23 11:25:32 startup archives unpack | 2008-06-23 11:25:32 upgrade dpkg 1.14.20 1.14.20 | 2008-06-23 11:25:32 status half-configured dpkg 1.14.20 | 2008-06-23 11:25:32 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:32 status half-installed dpkg 1.14.20 | 2008-06-23 11:25:32 status triggers-pending man-db 2.5.2-1 | 2008-06-23 11:25:33 status half-installed dpkg 1.14.20 | 2008-06-23 11:25:33 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:33 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:33 trigproc man-db 2.5.2-1 2.5.2-1 | 2008-06-23 11:25:33 status half-configured man-db 2.5.2-1 | 2008-06-23 11:25:37 status installed man-db 2.5.2-1 | 2008-06-23 11:25:46 startup packages configure | 2008-06-23 11:25:46 configure dpkg 1.14.20 1.14.20 | 2008-06-23 11:25:46 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:46 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:46 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:46 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:46 status unpacked dpkg 1.14.20 | 2008-06-23 11:25:46 status half-configured dpkg 1.14.20 | 2008-06-23 11:25:46 status installed dpkg 1.14.20 `---- This is the successful reinstallation, everything looks alright here. The only real problem seems the unexpected death of the dpkg process that performed the upgrade, but that is probably impossible to reconstruct. :-( Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
