Hi! On Fri, 2015-06-12 at 16:25:01 +0200, Niels Thykier wrote: > On 2015-06-12 15:36, Antonio Terceiro wrote: > > On Sat, May 30, 2015 at 07:46:02AM +0200, Niels Thykier wrote: > >> The output from dpkg suggests redmine has an /awaiting/ trigger cycle. > >> In particular, on itself? Indeed, redmine has the following triggers: > >> > >> """ > >> interest /usr/share/redmine/plugins > >> interest /usr/lib/ruby/vendor_ruby > >> """ > >> (From > >> http://anonscm.debian.org/cgit/pkg-ruby-extras/redmine.git/tree/debian/redmine.triggers) > > > > redmine does not install files on either of those locations, so how > > could it be triggering itself?
> Ok, admittedly look a bit weird. I am not sure what happened here and > leave it to the dpkg maintainers. Most of redmine dependencies ship files under /usr/lib/ruby/vendor_ruby. Which means when those packages activate the trigger, they get put in triggers-awaited, which does not satisfy dependencies, and then redmine cannot be configured or its triggers processed. The depending packages cannot get out of triggers-awaited until the pending trigger in redmine is processed. Thus the cycle. Hope this clarifies. 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/20150617032636.ga11...@gaara.hadrons.org
