Hi! 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. > > A solution to the above is to simply switch the triggers to their > > noawait variants, in this case from «interest» to «interest-noawait», > > That’s probably sensible anyway… > > > as long as they are not critical for the activating packages, which I > > cannot tell here. Otherwise a fix might unfortunatly be more involved. > > The idea is that, if a new version of mediawiki, or a new extension, > or a new version of an extension, is installed, that mediawiki’s > upgrade.php script is run on all wikis of the fusionforge wiki farm. > This need not be “right now”, but should be done in the same apt/dpkg > command group. So, a simple s/^interest/&-noawait/ on the triggers file > would be all that’s needed for that? Yes. It seems approrpiate, because here it's just enabling additional stuff from fusionforge-plugin-mediawiki side, and not something that the triggering packages are really concerned about. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
