Hi, On Sun, Dec 14, 2014 at 02:28:26PM +0100, Guillem Jover wrote: > On Fri, 2014-12-12 at 17:35:36 +0100, Thorsten Glaser wrote: > > So, with -noawait, the triggers just run later, but the dependency > > is satisfied early, right? > > Think of it as an asynchronouse notification that something changed in > another package vs a notification that the triggering package needs > something to be processed to be able to declare itself as configured. > > In case of -noawait, the triggering package never gets placed in a > triggers-awaited state, so it can always satisfy dependencies when it > has been configured.
So far my tests show that 'apt-get upgrade' doesn't start the noawait triggers. The fusionforge-plugin-mediawiki is marked 'triggers-pending' but apparently the user has to do something more manually, which is not satisfying. Any suggestion? > On Fri, 2014-12-12 at 17:40:43 +0100, b...@debian.org wrote: > > 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 > > dpkg was buggy and never performed dependency satisfiability checks > when trying to process triggers. This was fixed in dpkg 1.17.17. Well we didn't have any issue here either :/ http://buildbot.fusionforge.org/job/fusionforge-53-functests-deb/os=debian8/33/consoleFull However I can reproduce the problem by upgrading/downgrading mediawiki. How exactly did you "trigger" this bug? ;) -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
