[Pkg-utopia-maintainers] Bug#770627: pre-approval: unblock: dpkg/1.17.22

[Niels Thykier]

clone 771417 -1
retitle -1 dbus: Please (consider) switch(ing) to no-await triggers
reassign -1 dbus
found -1 1.8.12-1
# /Potential/ jessie blocker
severity -1 serious
thanks

@dbus maintainers, please review the feasibility of switching to
"no-await" triggers (see bottom of my email).  If not feasible, the new
bug against dbus can be downgraded to wishlist.

@apt+dpkg maintainers, please review the middle part.

On 2014-11-30 02:52, Guillem Jover wrote:
> Hi!
> 
> On Sat, 2014-11-29 at 12:20:45 +0100, Niels Thykier wrote:
>> [...]
> 
>> I just saw #771417, which claims dpkg to have made a regression.  I have
>> pulling my unblock until you have had a look at it.
> 
> Sure. As I mentioned on the bug, this is two issues in apt (#765687
> and #771428) and a minor one in dpkg (#771417), which I knew already
> but forgot to mention on the unblock request.

@apt + dpkg, for you:

The situation right now:
 * [apt]  #765687 is closed in sid (due to be unblocked)
 * [apt]  #765687 has David saying "known issue with
    dpkg << 1.17.21 and cannot be fixed in APT (with that version
    of dpkg)"
 * [dpkg] #771417 has Guillem saying "minor cosmetic" issue that
   cannot be fixed for Jessie.

Does this mean that apt/1.0.9.4 and dpkg/1.17.22 will "just work"(tm) or
do one of apt/dpkg need another update?  I got unblock requests for both
packages right now of which neither are active.
  What about "ordering" of the upgrades?  Do apt need to be upgraded
before dpkg (or vice versa) for this to work?

Personally, I am not fond of the idea of having to (potentially) "fix"
all packages using "regular" ("await"?) triggers.  That said, I am
willing to accept one or two fixes for trigger-consuming packages if it
will improve the upgrade experience.

> As I said on the bug,
> this is just a cosmetic issue, and because it should only happen due
> to problems elsewhere, I didn't consider it worth fixing for 1.17.x.
> 

@dbus: This part is for you.

> If this cannot be fixed in apt proper (due to requiring it to
> self-upgrade), then it should be fixable by switching dbus to
> noawaiting trigger directives (which I think would be correct
> regardless).
> 
> Thanks,
> Guillem
> 
> 

Thanks,
~Niels