On Fri, Dec 12, 2014 at 05:29:17PM +0100, Guillem Jover wrote: > On Fri, 2014-12-12 at 11:30:59 +0100, Thorsten Glaser wrote: > > On Thu, 11 Dec 2014, Guillem Jover wrote: > > > This package can get involved in a trigger cycle. The problem is that > > > it installs interests on /usr/share/mediawiki with files there > > > provided by mediawiki and mediawiki-classes, which are directly or > > > transitively depended on byfusionforge-plugin-mediawiki itself. > > > > Can you please explain how/why this can make trigger cycles? > > Sure. The fusionforge-plugin-mediawiki package is interested in a path, > that path is provided by say mediawiki, when installing mediawiki, > that package gets placed in triggers-awaited state (which does not > satisfy dependencies), and because to process the pending triggers in > fusionforge-plugin-mediawiki all dependencies need to be satisfied > dpkg cannot progress, and thus the trigger cycle. Hope that clarifies.
There's one point I'd like to clarify: how comes we never had any issues with this? E.g. I don't see any warning here: http://buildbot.fusionforge.org/job/fusionforge-53-functests-deb/os=debian7/33/consoleFull -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
