--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: wheezy -> jessie upgrade report: failure on dependency loop
- From: Antoine Beaupré <anarcat@koumbit.org>
- Date: Tue, 30 Dec 2014 21:00:10 -0500
- Message-id: <20141231020010.24628.80180.reportbug@angela.anarc.at>
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
My previous release is: wheezy
I am upgrading to: jessie
Upgrade date: 2014-12-30
uname -a before upgrade: Linux angela 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux
uname -a after upgrade: <The result of running uname -a on a shell prompt>
Method: apt-get dist-upgrade
Notice how i didn't do the multi-step process of first doing apt-get upgrade
then apt-get dist-upgrade, which I normally use at work. The reason is the
release notes explicitely state this is necessary only to reduce the downtime.
Since this is a single-user system, I figured I would test that theory. Maybe
the above wouldn't happen if the multi-step process was used.
Contents of /etc/apt/sources.list:
deb http://cdn.debian.net/debian jessie main contrib non-free
deb-src http://cdn.debian.net/debian jessie main contrib non-free
#deb http://ftp.debian.org/debian jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# sid sources
deb-src http://cdn.debian.net/debian sid main contrib non-free
- Were there any non-Debian packages installed before the upgrade? If
so, what were they?
yes, some packages related to bitmask.net and a package called
"koumbit-scripts" from work.
- Was the system pre-update a pure wheezy system? If not, which packages
were not from wheezy?
i think there may have been some backports.
- Did any packages fail to upgrade?
at this point, almost everything is stuck:
root@angela:/etc/apt/sources.list.d# apt-get dist-upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes.
Les paquets suivants contiennent des dépendances non satisfaites :
consolekit : Dépend: libck-connector0 (= 0.4.5-3.1) mais 0.4.6-5 est installé
libpam-systemd : Dépend: systemd (= 44-11+deb7u4) mais 215-8 est installé
lsof : Dépend: libperl4-corelibs-perl mais il n'est pas installé ou
perl (< 5.12.3-7) mais 5.20.1-4 est installé
lvm2 : Dépend: dmeventd (> 2:1.02.90) mais il n'est pas installé
systemd : Dépend: udev (>= 208-8) mais 175-7.2 est installé
E: Dépendances manquantes. Essayez d'utiliser l'option -f.
At that stage, i tried an "apt-get upgrade -f" followed by a dist-upgrade, and
things went a little more smoothly.
- Were there any problems with the system after upgrading?
Further Comments/Problems:
There are some prompts that do not seem necessary during the upgrade:
* localpurge asks me about dpkg, and I don't understand why, i think it should
do the right thing
* similarly, irqbalance asks me fairly technical stuff which a regular user is
unlikely to understand, it should also guess better
* base-passwd asked me repeatedly to confirm i wanted sane shells for system
accounts (daemon, gnats, bin, sys, games, man, lp, mail, news, uucp, proxy,
www-data, backup, list, irc) - not sure why they were set to /bin/sh, but if
it was the default in <=wheezy, this should have been done automatically
I also had problems upgrading slapd, but opened a separate bug report about it.
Emacs also had a bunch of trouble going to emacs24, mostly due to notmuch-emacs
freaking around with symbolic links (again?):
[...]
cp: impossible de créer le lien symbolique « ./notmuch-wash.el » vers « /usr/share/emacs/site-lisp/notmuch/notmuch-wash.el »: Le fichier existe
cp: impossible de créer le lien symbolique « ./notmuch.el » vers « /usr/share/emacs/site-lisp/notmuch/notmuch.el »: Le fichier existe
ERROR: install script from notmuch-emacs package failed
dpkg: erreur de traitement du paquet emacs24 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
This affects the packages emacs24, emacs and auctex. The problem is a space at the end:
root@angela:/etc/apt/sources.list.d# ls -al /usr/share/emacs/site-lisp/notmuch/notmuch-mua.el
ls: impossible d'accéder à /usr/share/emacs/site-lisp/notmuch/notmuch-mua.el : Aucun fichier ou dossier de ce type
root@angela:/etc/apt/sources.list.d# echo "ls -al /usr/share/emacs/site-lisp/notmuch/notmuch-mua.el " | hd
00000000 6c 73 20 2d 61 6c 20 2f 75 73 72 2f 73 68 61 72 |ls -al /usr/shar|
00000010 65 2f 65 6d 61 63 73 2f 73 69 74 65 2d 6c 69 73 |e/emacs/site-lis|
00000020 70 2f 6e 6f 74 6d 75 63 68 2f 6e 6f 74 6d 75 63 |p/notmuch/notmuc|
00000030 68 2d 6d 75 61 2e 65 6c c2 a0 0a |h-mua.el...|
0000003b
this is probably due to the locale (fr UTF8) yet even if i switch to the C locale, the problem remains:
cp: cannot create symbolic link ‘./notmuch-wash.el’ to ‘/usr/share/emacs/site-lisp/notmuch/notmuch-wash.el’: File exists
so there's something else fishy going on. i removed notmuch-emacs in the meantime to resolve the problem.
The isc-dhcp-server also fails to upgrade because i (deliberately) didn't
configure it /etc/default/isc-dhcp-server because i do *not* want to start it
on boot, but just on demand... The workaround there is to do an "exit 0" in the
defaults file.
I can provide a detailed transcript and logs and so on if necessary.
-- System Information:
Debian Release: 7.7
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: 774314-done@bugs.debian.org, Antoine Beaupré <anarcat@koumbit.org>
- Subject: Re: wheezy -> jessie upgrade report: failure on dependency loop
- From: Niels Thykier <niels@thykier.net>
- Date: Sun, 25 Jan 2015 11:44:56 +0100
- Message-id: <54C4C928.2030209@thykier.net>
- In-reply-to: <20141231020010.24628.80180.reportbug@angela.anarc.at>
- References: <20141231020010.24628.80180.reportbug@angela.anarc.at> <20141231020010.24628.80180.reportbug@angela.anarc.at>
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
--- End Message ---