On 2008-06-23 11:38 +0200, Jordi Mallach wrote: > As discussed with buxy on IRC, today I tried an upgrade, when my disk > filled up during trigger execution for package "dpkg". After this, I was > unable to configure dpkg. > > S'està preparant per a reemplaçar dpkg 1.14.19 (fent servir > .../dpkg_1.14.20_amd64.deb) ... > S'està desempaquetant el reemplaçament de dpkg ... > Processing triggers for man-db ... > [snip] > /usr/bin/mandb: no es pot crear la memòria cau d'índex > /var/cache/man/local/30906: No resta espai en el dispositiu > E: Sub-process /usr/bin/dpkg exited unexpectedly > > > After this, Dpkg failed with: > > dpkg: s'ha produït un error en processar dpkg (--configure): > el paquet dpkg no està llest per a configurar-se > no es pot configurar (estat actual «triggers-awaited») > S'han trobat errors en processar: > dpkg > E: Sub-process /usr/bin/dpkg returned an error code (1)
So dpkg remained in the state triggers-awaited because the trigger processing failed. This seems to be a reasonable outcome, although I could not find this situation documented in /usr/share/doc/dpkg/triggers.txt.gz. The diagram in that file seems to assume that the triggers are processed after "postinst configure", but in case of file triggers this is actually done after the triggering package (dpkg in this case) has been unpacked. See #484669. > Unpacking dpkg and then configuring it did the trick. Did you free some disk space in between and were the triggers for man-db processed again? > My broken /var/lib/dpkg/ can be retrieved from > http://people.debian.org/~jordi/varlibdpkg.tar.gz A copy of /var/log/dpkg.log would also be useful. Though it might be incomplete if dpkg could not write it due to lack of disk space. 8-) Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
