Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #76992

Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built

From Christoph Anton Mitterer <calestyo@scientia.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built
Date 2022-11-10 03:40 +0100
Message-ID <Fq5DX-2FK4-1@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Source: linux
Version: 6.0.7-1
Severity: normal


Hey.

When I tried out some recent patch from the intel folks for i915,
I built a custom kernel as described in:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official


Now before I installed the custom built debs, I wanted to make
sure the Debian ones are gone completely so I purged them, causing
apt to:
  Purging configuration files for linux-image-6.0.0-3-amd64 (6.0.7-1) ...
  W: Last kernel image has been removed, so removing the default symlinks
  rmdir: failed to remove '/lib/modules/6.0.0-3-amd64': Directory not empty

$ diff -qr --no-dereference /lib/modules/6.0.0-3-amd64/ 6.0.0-3-amd64/
Only in 6.0.0-3-amd64/: build
Only in 6.0.0-3-amd64/: source

with the former being again a completely fresh installation of the
Debian package, and the latter begin a copy from the Debian package's
dir, after I had built my custom kernel and before I purged the package.

l 6.0.0-3-amd64/build 6.0.0-3-amd64/source
lrwxrwxrwx 1 calestyo calestyo 36 Nov  5 14:41 6.0.0-3-amd64/build -> /usr/src/linux-headers-6.0.0-3-amd64
lrwxrwxrwx 1 calestyo calestyo 37 Nov  5 14:41 6.0.0-3-amd64/source -> /usr/src/linux-headers-6.0.0-3-common

I guess something during the build process creates these symlinks?


So either, that shouldn't happen in the first place. Or removing the
package should clean it up.
I'd guess the former?


Thanks,
Chris.




-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Back to linux.debian.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built Christoph Anton Mitterer <calestyo@scientia.org> - 2022-11-10 03:40 +0100
  Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built Christoph Anton Mitterer <calestyo@scientia.org> - 2022-11-10 03:50 +0100
    Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built Diederik de Haas <didi.debian@cknow.org> - 2022-11-10 11:10 +0100
  Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built Bastian Blank <waldi@debian.org> - 2022-11-10 13:10 +0100
    Bug#1023779: linux: deleting the kernel image package leaves back /lib/modules/<version> when a kernel package was built Christoph Anton Mitterer <calestyo@scientia.org> - 2022-11-10 14:20 +0100

csiph-web