[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#770627: dbus: Please (consider) switch(ing) to no-await triggers


On Thu, 2014-12-04 at 20:23:28 +0000, Simon McVittie wrote:
> Control: tags 771989 + moreinfo
> On Thu, 04 Dec 2014 at 16:39:31 +0100, Niels Thykier wrote:
> > On 2014-12-04 09:11, Simon McVittie wrote:
> [see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770627#70 for full
> analysis]

> > > If I am correct in my interpretation, then it seems to me that normal
> > > "interest" triggers are right here. However, if there is consensus that
> > > using the wrong trigger is a less severe bug than #771417, I can switch
> > > to "interest-noawait" and open a bug for "should go back to ordinary
> > > triggers post-jessie"... as long as that new bug is not *also* going to
> > > be considered RC.

> > If your interpretation is correct, then I am certainly not convinced
> > that changing the triggers to the "interest" variant is the correct
> > thing to do for dbus.
> >   Sadly, I am no expert on these matters, so I will have to defer it to
> > the APT or dpkg maintainers for whether your interpretation is correct.
> Thanks. apt/dpkg people: please send any feedback on the correct thing to do
> to <771989@bugs.debian.org>. Sorry, I mixed up the various bugs and
> didn't reply to that one initially; I have now bounced the missing
> messages to that bug (hopefully).

It seems the bounced mails didn't make it. In any case, from your
other mail:

> My question is, crucial for who? If dbus-daemon has not yet reloaded,
> then dbus-daemon will continue to work fine (it's in a consistent state
> either way), but the package that shipped the system service or security
> policy (in #771417 it's systemd) won't necessarily work properly until
> dbus-daemon has had a chance to reload.

Crucial for the awaiting package (I'll be updating the docs for 1.18.x).
So, from your explanation, then in this case they are crucial for the
activating packages yes, and the bug report against dbus can be closed.

Given this, the only options seem to be to possibly change the
--force-configure-any default to enabled (I'll try to test if this
helps in the dbus situation) which I'd rather not do (but oh well),
or disable the triggers dependency checks for jessie (and possibly
later releases, if apt does not get fixed for jessie) and go back
to the previous (broken, but known) behavior. :(


Reply to: