Bug#774314: wheezy -> jessie upgrade report: failure on dependency loop
Control: tags -1 moreinfo
On Tue, 30 Dec 2014 21:00:10 -0500 =?utf-8?q?Antoine_Beaupr=C3=A9?=
<anarcat@koumbit.org> wrote:
> Package: upgrade-reports
> Severity: important
>
> on my laptop, dist-upgrade from wheezy fails with:
>
> update-initramfs: deferring update (trigger activated)
> dpkg: boucle détectée durant le traitement des actions différées :
> listes des paquets qui en sont responsables (normalement)Â :
> gconf2 -> desktop-file-utils
> paquets bloqués par le traitement impossible d'actions différées requises :
> shared-mime-info: /usr/share/mime/packages
> doc-base: /usr/share/doc-base
> libc-bin: ldconfig
> initramfs-tools: update-initramfs
> desktop-file-utils: /usr/share/applications
> gconf2: /usr/share/gconf/schemas: /usr/share/gconf/defaults
> dpkg: erreur de traitement du paquet shared-mime-info (--configure)Â :
> bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
> Traitement des actions différées (« triggers ») pour libc-bin (2.19-13) ...
> Traitement des actions différées (« triggers ») pour initramfs-tools (0.115~bpo70+1) ...
> update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
> elilo: Not updating; /etc/elilo.conf not found
> Des erreurs ont été rencontrées pendant l'exécution :
> shared-mime-info
>
> [...]
Hi,
Sorry for the delayed responds time on our part.
At first glance, this appears to be #771730, which caused dpkg to report
trigger cycles that did not exist. This has been fixed in Jessie now.
The work around for a system affected by this is to run:
dpkg --configure --pending
Possibly repeated with "apt-get -f install" interleaved in between.
Unfortunately, your system might be in stuck with an old APT plus the
"broken" dpkg. I recommend that you ensure dpkg is upgraded as soon as
possible to avoid hitting this bug again followed by finishing the
upgrade of APT. Once these have been upgraded, you should be able to
continue the upgrade normally from there.
At the current time, most of our automated upgrade tests are green
regardless of whether you upgrade apt+dpkg first or not. But until
recently, the dpkg+apt in Jessie had several deficiencies (of which you
have experienced at least one).
Please note that we have a few known (actual) trigger cycles. These
currently involve gitweb and postgresql-common. Should you hit one of
those, the work around is to run dpkg --configure --pending and then
repeat the upgrade again.
Apologies for the mess and thanks for taking the time to report it,
~Niels
Reply to: