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

Bug#924743: marked as done (unblock: packagekit/1.1.12-5)



Your message dated Sun, 17 Mar 2019 07:22:00 +0000
with message-id <38140da7-58e6-5b81-3bc8-252a6f2bc852@thykier.net>
and subject line Re: Bug#924743: unblock: packagekit/1.1.12-5
has caused the Debian Bug report #924743,
regarding unblock: packagekit/1.1.12-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
924743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924743
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: unblock

Dear Release Team,
please consider unblocking packagekit 1.1.12-5.

This revision contains a lot of fixes compared to the one currently in testing:

* Add aptcc-frontend-locking.patch
  This implements APT frontend locking, which prevents other programs
  from stealing the dpkg lock in race conditions where apt(cc) has to
  release the lock in order to run dpkg.
  The APT team would really like to see this in Buster, as it prevents
a whole class of issues.

* Do not ship the GTK+2 plugin (Closes: #922118)
  We should never have shipped the GTK+2 plugin in a package the
explicitly mentions to be only for GTK+3. This restores the status quo
from a few PK releases where only the GTK+3 plugin was actually
present (the proper fix needs to happen upstream at some point).
This will allow the GNOME team and maybe other interested parties to
depend on the plugin without pulling in the legacy GTK+2.

* Remove Ubuntu-specific patch series, handle vendor config by
  conditionally installing it in d/rules (Closes: #915352)
  This change just makes the packagekit package more compliant to the
current policy.

* Add no-distupgrade.patch:
  - Disable GetDistroUpgrades() completely, it was partially
    disabled before but still caused problems.
  There are tons of bug reports about this in forums and the Ubuntu
bugtracker, so we really want this in Buster. We also don't want
anyone to attempt a dist-upgrade with PackageKit for now.

* Add keep-ref-on-transaction-while-doing-polkit-call.patch
  - Avoids some log spam

* Add aptcc-use-correct-return-type-in-function.patch:
  - Fix function return type, which resolves packagekitd crash
    when gnome-software launches, causing gnome-software to hang
    (Closes: #917812, #922236)
  This is a quite serious bug that happens because of an error in PK's
code combined wiith some odd compiler optimizations.

I don't see much potential for regressions, as all of these changes
are quite self-contained.
The individual patches are all upstreamed and can be reviewed at
https://salsa.debian.org/pkgutopia-team/packagekit/tree/master/debian/patches
as well.

Thank you for considering!
    Matthias Klumpp

unblock packagekit/1.1.12-5

--- End Message ---
--- Begin Message ---
Matthias Klumpp:
> Package: release.debian.org
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> please consider unblocking packagekit 1.1.12-5.
> 
> This revision contains a lot of fixes compared to the one currently in testing:
> 
> [...]
> 
> I don't see much potential for regressions, as all of these changes
> are quite self-contained.
> The individual patches are all upstreamed and can be reviewed at
> https://salsa.debian.org/pkgutopia-team/packagekit/tree/master/debian/patches
> as well.
> 
> Thank you for considering!
>     Matthias Klumpp
> 
> unblock packagekit/1.1.12-5
> 

Unblocked, thanks.
~Niels

--- End Message ---

Reply to: