Your message dated Wed, 3 Mar 2010 12:22:22 -0500
with message-id <[email protected]>
and subject line Re: [Pkg-dkms-maint] Bug#571683: dkms: should dkms clean up
after itself?
has caused the Debian Bug report #571683,
regarding dkms: should dkms clean up after itself?
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 [email protected]
immediately.)
--
571683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: dkms
version: 2.1.1.2-2
severity: normal
when removing a kernel which has previously had dkms modules built
for it, the user will see the following message:
rmdir: failed to remove `/lib/modules/2.6.32-2-amd64': Directory not empty
dpkg: warning: while removing linux-image-2.6.32-2-amd64, directory
'/lib/modules/2.6.32-2-amd64' not empty so not removed.
this is because dkms doesn't have any cleanup code to remove the
modules and files it creates. would it be make sense to add some
dkms cleanup code to the kernel's postrm? if i find the time, i
will look into this (if it sounds reasonable).
mike
--- End Message ---
--- Begin Message ---
On Wed, 03 Mar 2010 16:37:15 +0100, Giuseppe Iuculano wrote:
> Il 27/02/2010 08:04, Michael Gilbert ha scritto:
> > this is because dkms doesn't have any cleanup code to remove the
> > modules and files it creates. would it be make sense to add some
> > dkms cleanup code to the kernel's postrm? if i find the time, i
> > will look into this (if it sounds reasonable).
> >
>
> Strange.. we have already /etc/kernel/prerm.d/dkms
hmmm, looks like i didn't look closely enough.
i just tested this again, and can't reproduce it. maybe since my
original report was for an older kernel that was installed with an
older dkms the remove scripts weren't called for some reason.
anyway, i'm closing the bug and will reopen if it happens again in the
future. but it was probably just a temporary issue.
mike
--- End Message ---
