[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#359816: marked as done (nvidia-kernel-2.6.15-1-k7: Unable to purge package)

Your message dated Sun, 07 May 2006 02:00:51 +0100
with message-id <E1FcXdj-0003Bj-AM@xerces>
and subject line Fixed by grub
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: nvidia-kernel-2.6.15-1-k7
Version: 2.6.15-8
Severity: normal

I am unable to purge the package:

(Reading database ... 173358 files and directories currently installed.)
Removing linux-image-2.6.15-1-k7 ...
Purging configuration files for linux-image-2.6.15-1-k7 ...
debconf: unable to initialize frontend: Gnome
debconf: (Can't locate object method "signal_connect" via package
"Gtk2::Window" at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 66.)
debconf: falling back to frontend: Dialog
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub .
dpkg: error processing linux-image-2.6.15-1-k7 (--purge):
 subprocess post-removal script returned error exit status 128
 Errors were encountered while processing:
  linux-image-2.6.15-1-k7
  

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-1-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages nvidia-kernel-2.6.15-1-k7 depends on:
ii  nvidia-kernel-common          20051028+1 NVIDIA binary kernel module common

--- End Message ---
--- Begin Message --- 
Turns out this was grub 0.95's fault, and no one cares about an obsolete linux-image package anyway. :)

--- End Message ---
Reply to: