Control: unmerge 768598 Control: reassign 768598 fontconfig 2.6.0-4 Control: block -1 by 768598 Control: unmerge 768600 Control: clone 768600 -2 Control: retitle -2 dpkg: "src/packages.c:226: process_queue: Assertion `dependtry <= 4' failed." due to trigger cycles? Control: severity -2 important Control: tags -2 moreinfo Control: reassign 768600 readahead-fedora 1.5.0-6 Control: block -1 by 768600
[ Maintainers for reassigned bugs BCCed. ] On Sat, 2014-11-08 at 22:32:21 +0000, Emilio Pozuelo Monfort wrote: > Control: reassign 768598 dpkg 1.17.21 > Control: reassign 768600 dpkg 1.17.21 > Control: forcemerge -1 768598 768600 > Control: affects -1 man-db font-config readhead-fedora > On 08/11/14 17:38, Guillem Jover wrote: > >On Sat, 2014-11-08 at 16:56:33 +0000, Colin Watson wrote: > >>On Sat, Nov 08, 2014 at 04:05:17PM +0000, Holger Levsen wrote: > >>>package: man-db > >>>severity: serious > >>>x-debbugs-cc: debian-dpkg@lists.debian.org > > > >>>Setting up startpar (0.59-3) ... > >>>Installing new version of config file /etc/init/startpar-bridge.conf ... > >>>dpkg: cycle found while processing triggers: > >>> chain of packages whose triggers are or may be responsible: > >>> man-db -> man-db > >>> packages' pending triggers which are or may be unresolvable: > >>> man-db: /usr/share/man > >>>dpkg: error processing package man-db (--configure): > >>> triggers looping, abandoned > >>>Setting up sysvinit-utils (2.88dsf-57) ... > >>>Errors were encountered while processing: > >>> man-db > >>>E: Sub-process /usr/bin/dpkg returned an error code (1) > >> > >>This has got to be a dpkg bug. There's no good reason for a package not > >>to be able to trigger itself, and this has worked for ages. Just to clarify on this point. This has worked for ages only because dpkg was not checking dependency satisfiability when processing triggers, so it was just not detected before. Regarding the self-triggering, I've been thinking about this too for some time, and I've to agree it might be sensible to possibly allow it as it kind of makes sense conceptually, as the package should know how to make itself usable, although I don't see that case being defined in the triggers spec, in fact by a strict reading it should not be allowed at all (AFAICS?). In any case this does not affect current man-db, as per below. > >That's because (according to the log), the man-db package being > >triggered (version 2.6.2-1) is the one still using the awaiting > >interest directive, which got switched to interest-noawait in 2.6.3-6. > > > >I'll have to add Breaks for any such packages. :/ But I'm not sure how > >much that might make the upgrade more difficult, as dpkg contains > >already many Breaks/Conflicts. > > Also font-config (#768598) / readahead-fedora (#768600). But my above quoted comment does not apply to these two bugs, as they are still using awaiting trigger directives. So they need to be switched to the noawait variants first. Then I'll be able to add Breaks/Conflicts. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109164559.ga26...@gaara.hadrons.org
