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

Groups > linux.debian.kernel > #82781 > unrolled thread

Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Diederik de Haas <didi.debian@cknow.org> - 2024-06-21 13:40 +0200
    Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Christoph Berg <myon@debian.org> - 2024-06-21 13:50 +0200
      Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Diederik de Haas <didi.debian@cknow.org> - 2024-06-21 14:10 +0200
        Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Salvatore Bonaccorso <carnil@debian.org> - 2024-06-22 11:00 +0200
    Processed: Re: Bug#1073998: linux: Purging linux-image-<version>  doesn't clean up modules.weakdep file "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-21 14:10 +0200
    Processed: Re: Bug#1073998: linux: Purging linux-image-<version>  doesn't clean up modules.weakdep file "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-22 11:00 +0200
    Bug#1073998: marked as done (linux: Purging linux-image-<version>  doesn't clean up modules.weakdep file) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-22 12:30 +0200
    Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Salvatore Bonaccorso <carnil@debian.org> - 2024-06-22 13:20 +0200
    Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Vincent Lefevre <vincent@vinc17.net> - 2024-10-04 16:00 +0200
      Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Salvatore Bonaccorso <carnil@debian.org> - 2024-10-06 17:10 +0200
        Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Vincent Lefevre <vincent@vinc17.net> - 2024-10-06 17:40 +0200
          Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file Salvatore Bonaccorso <carnil@debian.org> - 2024-10-06 19:40 +0200

#82781 — Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file

Source: linux
Version: 6.9.2-1
Severity: minor

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

When removing or 'even' purging a linux-image-<version> package, it
reports the following issue:

rmdir: failed to remove '/lib/modules/<version>': Directory not empty

The reason for that is that there's still a ``modules.weakdep`` file.
It seems to me that at least with purging that file should be removed
and subsequently the ``/lib/modules/<version>`` dir.

FWIW: I do not have any DKMS package which could also result in the
inability to remove the modules dir.

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZnVlCwAKCRDXblvOeH7b
bvdqAPwOCZQoQ5xXUbW+FkytY5Ovj5xoPizPFOWdFTvtaXro0QD/RhTTHvmL4cZ4
GfAOEDPN4Rv+vnze+lNZt+xCrTSa4AY=
=QCxl
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#82782

Re: Diederik de Haas
> When removing or 'even' purging a linux-image-<version> package, it
> reports the following issue:
> 
> rmdir: failed to remove '/lib/modules/<version>': Directory not empty
> 
> The reason for that is that there's still a ``modules.weakdep`` file.

I just had the same problem on linux-image-6.6.15-amd64.

> It seems to me that at least with purging that file should be removed
> and subsequently the ``/lib/modules/<version>`` dir.

TBH, I'd even argue plain "remove" should remove the debris from the
modules directory, it's not like there's anything of value in the
modules.* files left behind.

Kernels are the only package that I'm actually purging, if "remove"
wouldn't leave /lib/modules/*/ behind, I wouldn't have to do that.

Christoph

[toc] | [prev] | [next] | [standalone]

#82785

[Multipart message — attachments visible in raw view] — view raw

Control: found -1 6.6.15-1

On Friday, 21 June 2024 13:41:38 CEST Christoph Berg wrote:
> I just had the same problem on linux-image-6.6.15-amd64.

Updating found version accordingly.

> > It seems to me that at least with purging that file should be removed
> > and subsequently the ``/lib/modules/<version>`` dir.
> 
> TBH, I'd even argue plain "remove" should remove the debris from the
> modules directory, it's not like there's anything of value in the
> modules.* files left behind.

I didn't have that many kernels installed, so I only verified it with 1 and for 
that I used 'purge'. But I'm inclined to agree that remove should remove that 
file too.

[toc] | [prev] | [next] | [standalone]

#82793

Control: tags -1 + moreinfo

Hi Diederik,

On Fri, Jun 21, 2024 at 01:47:59PM +0200, Diederik de Haas wrote:
> Control: found -1 6.6.15-1
> 
> On Friday, 21 June 2024 13:41:38 CEST Christoph Berg wrote:
> > I just had the same problem on linux-image-6.6.15-amd64.
> 
> Updating found version accordingly.
> 
> > > It seems to me that at least with purging that file should be removed
> > > and subsequently the ``/lib/modules/<version>`` dir.
> > 
> > TBH, I'd even argue plain "remove" should remove the debris from the
> > modules directory, it's not like there's anything of value in the
> > modules.* files left behind.
> 
> I didn't have that many kernels installed, so I only verified it with 1 and for 
> that I used 'purge'. But I'm inclined to agree that remove should remove that 
> file too.

Are you sure about the found version 6.9.2-1~exp1? With the
https://salsa.debian.org/kernel-team/linux/-/commit/19656787a6b4dcb29ea999a91cb9eb5e7994d77f
merge this is actually fixed for 6.9.2-1~exp1.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#82784 — Processed: Re: Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file

Processing control commands:

> found -1 6.6.15-1
Bug #1073998 [src:linux] linux: Purging linux-image-<version> doesn't clean up modules.weakdep file
Marked as found in versions linux/6.6.15-1.

-- 
1073998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073998
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#82792 — Processed: Re: Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file

Processing control commands:

> tags -1 + moreinfo
Bug #1073998 [src:linux] linux: Purging linux-image-<version> doesn't clean up modules.weakdep file
Added tag(s) moreinfo.

-- 
1073998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073998
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#82801 — Bug#1073998: marked as done (linux: Purging linux-image-<version> doesn't clean up modules.weakdep file)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 22 Jun 2024 12:13:26 +0200
with message-id <1964824.qjskfCstz5@bagend>
and subject line Re: Bug#1073998: linux: Purging linux-image-<version> doesn't clean up modules.weakdep file
has caused the Debian Bug report #1073998,
regarding linux: Purging linux-image-<version> doesn't clean up modules.weakdep file
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.)


-- 
1073998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073998
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#82805

On Sat, Jun 22, 2024 at 12:13:26PM +0200, Diederik de Haas wrote:
> Version: 6.9.2-1~exp1
> 
> On Saturday, 22 June 2024 10:52:53 CEST Salvatore Bonaccorso wrote:
> > Are you sure about the found version 6.9.2-1~exp1? With the
> > https://salsa.debian.org/kernel-team/linux/-/commit/19656787a6b4dcb29ea999a9
> > 1cb9eb5e7994d77f merge this is actually fixed for 6.9.2-1~exp1.
> 
> Wow, do I feel stupid now :-O
> You're absolutely right, purging 6.9.2-1~exp1 does succeed.
> 
> I could reproduce it when removing *my* 6.9.2 kernel (on arm64) ... but that 
> build/kernel did not have that commit. (In my poor defense)

Diederik, thanks for your quick confirmation and updating the bug
metadata.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84185

This bug has been fixed in unstable kernels. Shouldn't it be fixed
in stable kernels too (as the fix is rather trivial)?

For instance, I still have

-rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep

while the kernel has been purged. So I got

Purging configuration files for linux-image-6.1.0-25-amd64 (6.1.106-3) ...
rmdir: failed to remove '/lib/modules/6.1.0-25-amd64': Directory not empty
dpkg: warning: while removing linux-image-6.1.0-25-amd64, directory '/lib/modules/6.1.0-25-amd64' not empty so not removed

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#84207

Hi Vincent,

On Fri, Oct 04, 2024 at 03:48:10PM +0200, Vincent Lefevre wrote:
> This bug has been fixed in unstable kernels. Shouldn't it be fixed
> in stable kernels too (as the fix is rather trivial)?
> 
> For instance, I still have
> 
> -rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep
> 
> while the kernel has been purged. So I got
> 
> Purging configuration files for linux-image-6.1.0-25-amd64 (6.1.106-3) ...
> rmdir: failed to remove '/lib/modules/6.1.0-25-amd64': Directory not empty
> dpkg: warning: while removing linux-image-6.1.0-25-amd64, directory '/lib/modules/6.1.0-25-amd64' not empty so not removed

Can you elaborate how you ended in this situation for stable? The
issue is actually in combination with only recent kmod, which
introduced creating the modules.weakdep. It should have been with kmod
around v32+20240327, so nothing around stable.

Can you give some background information on your system? Is there a
newer kmod installed from the upper suite or is this after an upgrade
to trixie actually?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84208

On 2024-10-06 16:59:17 +0200, Salvatore Bonaccorso wrote:
> Hi Vincent,
> 
> On Fri, Oct 04, 2024 at 03:48:10PM +0200, Vincent Lefevre wrote:
> > This bug has been fixed in unstable kernels. Shouldn't it be fixed
> > in stable kernels too (as the fix is rather trivial)?
> > 
> > For instance, I still have
> > 
> > -rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep
> > 
> > while the kernel has been purged. So I got
> > 
> > Purging configuration files for linux-image-6.1.0-25-amd64 (6.1.106-3) ...
> > rmdir: failed to remove '/lib/modules/6.1.0-25-amd64': Directory not empty
> > dpkg: warning: while removing linux-image-6.1.0-25-amd64, directory '/lib/modules/6.1.0-25-amd64' not empty so not removed
> 
> Can you elaborate how you ended in this situation for stable? The
> issue is actually in combination with only recent kmod, which
> introduced creating the modules.weakdep. It should have been with kmod
> around v32+20240327, so nothing around stable.

This is a Debian/unstable machine where I keep the latest stable
kernel installed in case anything goes wrong with the unstable
kernels.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#84218

Hi Vincent,

On Sun, Oct 06, 2024 at 05:36:45PM +0200, Vincent Lefevre wrote:
> On 2024-10-06 16:59:17 +0200, Salvatore Bonaccorso wrote:
> > Hi Vincent,
> > 
> > On Fri, Oct 04, 2024 at 03:48:10PM +0200, Vincent Lefevre wrote:
> > > This bug has been fixed in unstable kernels. Shouldn't it be fixed
> > > in stable kernels too (as the fix is rather trivial)?
> > > 
> > > For instance, I still have
> > > 
> > > -rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep
> > > 
> > > while the kernel has been purged. So I got
> > > 
> > > Purging configuration files for linux-image-6.1.0-25-amd64 (6.1.106-3) ...
> > > rmdir: failed to remove '/lib/modules/6.1.0-25-amd64': Directory not empty
> > > dpkg: warning: while removing linux-image-6.1.0-25-amd64, directory '/lib/modules/6.1.0-25-amd64' not empty so not removed
> > 
> > Can you elaborate how you ended in this situation for stable? The
> > issue is actually in combination with only recent kmod, which
> > introduced creating the modules.weakdep. It should have been with kmod
> > around v32+20240327, so nothing around stable.
> 
> This is a Debian/unstable machine where I keep the latest stable
> kernel installed in case anything goes wrong with the unstable
> kernels.

Thanks for the confirmation.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web