Hi! On Mon, 2014-12-01 at 23:26:32 +0100, Andreas Beckmann wrote: > Package: dpkg > Version: 1.17.22 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts
> with the latest dpkg I still get a trigger cycle error on a wheezy->sid > piuparts upgrade test: > > Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2) ... > Setting up dmsetup (2:1.02.90-2) ... > update-initramfs: deferring update (trigger activated) > dpkg: cycle found while processing triggers: > chain of packages whose triggers are or may be responsible: > initramfs-tools -> libc-bin > packages' pending triggers which are or may be unresolvable: > libc-bin: ldconfig > initramfs-tools: update-initramfs > dpkg: error processing package libc-bin (--configure): > triggers looping, abandoned > Errors were encountered while processing: > libc-bin > > Just verified that this is repeatable in piuparts and not a one-off > failure. > > The new dpkg was long installed and configured before this happened. > Full log attached: nvidia-kernel-amd64_340.46+3.16.0+2.log.gz > > I could not reproduce this in an upgrade from wheezy->jessie (i.e. with > dpkg 1.17.21), full log: nvidia-kernel-amd64=340.46+3.16.0+1.log.gz > but of course there are more package versions different ... > If you need more debug information, tell me how to aquire it. > > I'm rather opening a new bug than messing with the ones that are supposed > to be fixed in 1.17.22. This could be an independent issue or needs to be > reassigned to another package ... Feel free to downgrade the severity to > not block 1.17.22 from migrating - which should be a good improvement > over 1.17.21. I'll take a proper look once I wake up, if I need more info I'll ask for it, thanks! Regards, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
