Your message dated Thu, 18 Aug 2022 02:22:01 +0200
with message-id 
<caknhny9kpvkstvfe1gztctn7kwbzpqyetzyckjwg-20tant...@mail.gmail.com>
and subject line Re: Bug#1017532: packagekit: please do the equivalent of "apt 
autoremove" after upgrades
has caused the Debian Bug report #1017532,
regarding packagekit: please do the equivalent of "apt autoremove" after 
upgrades
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 ow...@bugs.debian.org
immediately.)


-- 
1017532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: packagekit
Version: 1.2.5-3
Severity: wishlist

Dear Maintainer,

I help a few friends whore are not into software run Debian on their
machines. They do updates through gnome-software and PackageKit, and
this works well.

However, after a few stable updates, there are several kernels
installed, and /boot will often fill up. At this point GNOME will show
them warnings about /boot having little available space, and I have to
intervene running `apt autoremove` for them to make the warnings go
away.

It would be nice if the PackageKit APT backend would perform the
equivalent of `apt autoremove` on each upgrade.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages packagekit depends on:
ii  init-system-helpers     1.64
ii  libappstream4           0.15.4-1
ii  libapt-pkg6.0           2.5.2
ii  libc6                   2.34-3
ii  libgcc-s1               12.1.0-8
ii  libglib2.0-0            2.72.3-1+b1
ii  libglib2.0-bin          2.72.3-1+b1
ii  libgstreamer1.0-0       1.20.3-1
ii  libpackagekit-glib2-18  1.2.5-3
ii  libpolkit-gobject-1-0   0.105-33
ii  libsqlite3-0            3.39.2-1
ii  libstdc++6              12.1.0-8
ii  libsystemd0             251.3-1
ii  policykit-1             0.105-33

Versions of packages packagekit recommends:
ii  packagekit-tools  1.2.5-3
ii  systemd           251.3-1

Versions of packages packagekit suggests:
ii  appstream  0.15.4-1

-- no debconf information

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Hi Antonio!

Am Mi., 17. Aug. 2022 um 18:09 Uhr schrieb Antonio Terceiro
<terce...@debian.org>:
> [...]
> I help a few friends whore are not into software run Debian on their
> machines. They do updates through gnome-software and PackageKit, and
> this works well.
>
> However, after a few stable updates, there are several kernels
> installed, and /boot will often fill up. At this point GNOME will show
> them warnings about /boot having little available space, and I have to
> intervene running `apt autoremove` for them to make the warnings go
> away.
>
> It would be nice if the PackageKit APT backend would perform the
> equivalent of `apt autoremove` on each upgrade.

I've actually fixed this with PackageKit 1.2.5, PK will use APTs own
support for removing older kernels. Unfortunately, this change was
extremely invasive and required quite a bit of refactoring in our
APTcc backend as well as other components (such as gnome-software), so
we can't really backport this change easily.
This problem is however addressed for Debian 12 (likely to be released
next year). Any testing of this feature with bookworm is very welcome,
it would be nice to iron out any possible issues before the release is
made. Thanks for reporting this issue!

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

--- End Message ---

Reply via email to