Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Old kernel versions not removed properly
Date: Sun, 04 Feb 2024 07:08:33 +0100	[thread overview]
Message-ID: <20240204060833.77F0F2B9E1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48511@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

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

Comment:
Your removal process eliminated various kernels but left their headers installed. As you subsequently upgrade the system and, along with it, various header packages, you leave behind the old headers (by design---that's why vkpurge exists). However, vkpurge looks for actual kernels to identify candidates for removal. Because you've already eliminated the kernels, vkpurge never considers the stray headers for removal.

The fix here is to manually remove these left-behind kernel headers, maybe clean up your DKMS installation, throw away the useless initramfs images and, in the future, remember that any removal of the kernel package should be paired with removal of the corresponding header package. 

  parent reply	other threads:[~2024-02-04  6:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 17:31 [ISSUE] " joshuakraemer
2024-02-03 17:57 ` Chocimier
2024-02-03 18:19 ` joshuakraemer
2024-02-04  6:08 ` ahesford [this message]
2024-02-04  6:08 ` [ISSUE] [CLOSED] " 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=20240204060833.77F0F2B9E1@inbox.vuxu.org \
    --to=ahesford@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).