Github messages for voidlinux
 help / color / mirror / Atom feed
From: joshuakraemer <joshuakraemer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Old kernel versions not removed properly
Date: Sat, 03 Feb 2024 18:31:19 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48511@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4092 bytes --]

New issue by joshuakraemer on void-packages repository

https://github.com/void-linux/void-packages/issues/48511

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.5_2 x86_64 GenuineIntel uptodate rrrrmmnFFFFFFFFFFFFF

### Package(s) Affected

xbps-0.59.2_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Before each system update, I check for installed kernels with `xbps-query --regex -s '^linux[0-9.]+-[0-9._]+'`, remove old kernel packages with `xbps-remove -Rf linuxX.X` and remove old kernels with `vkpurge rm all`. I expect all old kernels to be removed completely by those commands, including the corresponding header packages.

### Actual behaviour

Despite the procedure described above, old kernels don't seem to be removed properly. After an update carried out today, there are still multiple old header packages installed:
```
% xbps-query --regex -s '^linux[0-9]'
[*] linux6.0-headers-6.0.19_1 Linux kernel and modules (6.0 series) - source headers for 3rd party modules
[*] linux6.1-headers-6.1.71_1 Linux kernel and modules (6.1 series) - source headers for 3rd party modules
[*] linux6.3-headers-6.3.13_2 Linux kernel and modules (6.3 series) - source headers for 3rd party modules
[*] linux6.5-6.5.13_1         Linux kernel and modules (6.5 series)
[*] linux6.5-headers-6.5.13_1 Linux kernel and modules (6.5 series) - source headers for 3rd party modules
[*] linux6.6-6.6.11_1         Linux kernel and modules (6.6 series)
[*] linux6.6-headers-6.6.11_1 Linux kernel and modules (6.6 series) - source headers for 3rd party modules
```

During the update, DKMS modules for 9 kernels have been built (those even include kernel versions for which no headers are installed):
```
nvidia-dkms-535.154.05_1: configuring ...
Added DKMS module 'nvidia-535.154.05'.
Skipping kernel-5.13.19_1. kernel-headers package not installed...
Building DKMS module 'nvidia-535.154.05' for kernel-5.15.60_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-5.15.60_1... done.
Skipping kernel-5.19.17_1. kernel-headers package not installed...
Building DKMS module 'nvidia-535.154.05' for kernel-6.0.19_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.0.19_1... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.1.46_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.1.46_1... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.1.55_2... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.1.55_2... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.1.71_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.1.71_1... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.3.13_2... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.3.13_2... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.5.13_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.5.13_1... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.5.5_2... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.5.5_2... done.
Building DKMS module 'nvidia-535.154.05' for kernel-6.6.11_1... done.
Installing DKMS module 'nvidia-535.154.05' for kernel-6.6.11_1... done.
```

Files in /boot/:
```
config-6.5.13_1
config-6.5.5_2
config-6.6.11_1
efi
grub
initramfs-5.15.60_1.img
initramfs-6.0.19_1.img
initramfs-6.1.46_1.img
initramfs-6.1.55_2.img
initramfs-6.1.71_1.img
initramfs-6.3.13_2.img
initramfs-6.5.13_1.img
initramfs-6.5.5_2.img
initramfs-6.6.11_1.img
vmlinuz-6.5.13_1
vmlinuz-6.5.5_2
vmlinuz-6.6.11_1
```

### Steps to reproduce

1. Check for installed kernels with `xbps-query --regex -s '^linux[0-9.]+-[0-9._]+'`
2. Remove all old kernel packages with `xbps-remove -Rf linuxX.X`
3. Remove all old kernels with `vkpurge rm all`
4. Update system with `xbps-install -Su`
5. Check for old header packages with `xbps-query --regex -s '^linux[0-9.]+-headers'`
6. Check for old kernel files in /boot/

             reply	other threads:[~2024-02-03 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 17:31 joshuakraemer [this message]
2024-02-03 17:57 ` Chocimier
2024-02-03 18:19 ` joshuakraemer
2024-02-04  6:08 ` [ISSUE] [CLOSED] " ahesford
2024-02-04  6:08 ` ahesford
2024-02-04 10:55 ` joshuakraemer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48511@inbox.vuxu.org \
    --to=joshuakraemer@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).