Your message dated Sun, 25 Jan 2015 11:33:47 +0100 with message-id <[email protected]> and subject line Re: wheezy->jessie: trigger loop gconf2 -> initramfs-tools has caused the Debian Bug report #774493, regarding wheezy->jessie: trigger loop gconf2 -> initramfs-tools to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 774493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774493 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: upgrade-reports Severity: serious Heya, I've just upgraded a family laptop from wheezy to jessie. The general experience has been very good and quick, with no noticeable breakages. The only problem is that the first "apt-get dist-upgrade" (after an "apt-get upgrade", as recommended by the release notes) failed due to a trigger loop. Here are the details (messages translated to English by hand, as the upgraded laptop had an Italian locale) : configuring libdevmapper1.02.1:amd64 (2:1.02.90-2) trigger loop detected potentially responsible packages: gconf2 -> initramfs-tools awaiting triggers that might be non resolvable libc-bin: ldconfig initramfs-tools: update-initramfs gconf2: /usr/share/gconf/schemas dpkg: error while processing libc-bin (--configure): trigger loop, giving up (If needed, I have a picture of the tty console on my phone, which I can provide.) After a few "dpkg --configure --pending" / "apt-get -f install" the problem went away and I managed to succesfully complete "apt-get dist-upgrade". Cheers. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---On 2015-01-03 14:33, Stefano Zacchiroli wrote: > On Sat, Jan 03, 2015 at 02:24:43PM +0100, Niels Thykier wrote: >> Seems to be #771730, so it should disappear once the new dpkg migrates. > > Thanks. I've looked into the bug reports of the mentioned packages for > duplicates, but didn't look into dpkg itself. > >> Would be possible for you to re-try the upgrade where you upgrade into >> the dpkg from sid instead of the Jessie version? > > Unfortunately not :-/, as the laptop has been upgraded now, and I don't > have handy another laptop with a similar/identical configuration. > > Cheers. > Ok, thanks. I am taking the liberty of closing this, as I strongly suspect it has been fixed in dpkg now and all known trigger cycles[1] do not include the packages from your APT output. If you manage to reproduce it with the current dpkg from testing, please do not hesitate to reopen it. Thanks, ~Niels [1] https://jenkins.debian.net/job/dpkg_testing_find_trigger_cycles/
--- End Message ---
