Bug#401865: linux-image-2.6.18-3-686: post-removal script returns error exit status 128
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: normal
I tried to completely remove the package (with --purge option) but the
configuration files remain. This problem is found on builds 6 and 7.
MICU:~# aptitude purge linux-image-2.6.18-3-686
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages will be REMOVED:
linux-image-2.6.18-3-686{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 50.8MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 117949 files and directories currently installed.)
Removing linux-image-2.6.18-3-686 ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.17-2-686
Updating /boot/grub/menu.lst ... done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
Purging configuration files for linux-image-2.6.18-3-686 ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.17-2-686
Updating /boot/grub/menu.lst ... done
dpkg: error processing linux-image-2.6.18-3-686 (--purge):
subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
linux-image-2.6.18-3-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-3-686 depends on:
ii coreutils 5.97-5 The GNU core utilities
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs
ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-3-686 recommends:
ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/kimage-is-a-directory:
linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false
linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false
linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.19, kernel-package problems and what are our plans for etch ...
-2.6-xen-686, squashfs-modules-2.6-xen-k7, squashfs-modules-2.6.17-2-486, squashfs-modules-2.6.17-2-686, squashfs-modules-2.6.17-2-686-bigmem, squashfs-modules-2.6.17-2-k7, squashfs-modules-2.6.17-2-vserver-686, squashfs-modules-2.6.17-2-vserver-k7, squashfs-modules-2.6.17-2-xen-686, squashfs-modules-2.6.17-2-xen-k7, unionfs-modules-2.6-486, unionfs-modules-2.6-686, unionfs-modules-2.6-686-bigmem, unionfs-modules-2.6-k7, unionfs-modules-2.6.17-2-486, unionfs-modules-2.6.17-2-686, unionfs-modules-2.6.17-2-686-bigmem, unionfs-modules-2.6.17-2-k7 I could use a force-hint on linux-modules-extra-2.6 as well, but as long as it is out-of-date on so many architectures, that won't improve the picture. And also, why do e.g. linux-image-2.6-vserver-k7 get uninstallable (hm, that could be a bug in britney though). Ok, this is the linux-modules-extra-2.6 problem, which should be solved by removing the module which is broken. not sure which one it was. The -k7 issue, i don't know, can it be a flavour that was dropped or something ? - What are our plans for 2.6.19 ? Will we have it enter unstable, and maintain the etch kernel through testing-proposed-updates ? I heard this mentioned some time back. Will we fork a linux-2.6.19 package in unstable ? Will we keep 2.6.19 in experimental for now ? I hope you can keep 2.6.19 in experimental for now - it doesn't take so long to release Etch anymore. Bah, we where told this for sarge, and it took over a year back then. I don't see us releaseing etch anytime soon, since we don't have had a single release candidate of d-i with the 2.6.18 kernels in it yet, so moving 2.6.19 to unstable (maybe with a linux-2.6.19 source package) should be nice enough. We did this already for 2.6.16, so, we know how to do this. Friendly, Sven Luther -- Teodor-Adrian MICU Consultant TIC [EMAIL PROTECTED]
