Message-ID: <email address hidden>
Date: Sun, 25 Dec 2005 22:57:12 +0100
From: Cesare Leonardi <email address hidden>
To: <email address hidden>
Subject: Lock during kernel 2.6.14 purge
Package: linux-image-2.6-386
Version: 2.6.14-6
Trying to purge that package you get the following situation (purge
launched from aptitude):
----------------------
(Reading database ... 80461 files and directories currently installed.)
Removing linux-image-2.6-386 ...
Removing linux-image-2.6.14-2-386 ...
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.14-2-686
Found kernel: /boot/vmlinuz-2.6.12-1-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 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 lilo
Purging configuration files for linux-image-2.6.14-2-386 ...
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.14-2-686
Found kernel: /boot/vmlinuz-2.6.12-1-686
Updating /boot/grub/menu.lst ... done
----------------------
At that point the purging procedure seems locked (i have waited over a
minute) and i have to press CTRL+C. Then the output is:
----------------------
dpkg: error processing linux-image-2.6.14-2-386 (--purge):
subprocess post-removal script killed by signal (Interrupt)
Errors were encountered while processing:
linux-image-2.6.14-2-386
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.
----------------------
I have verified such behaviour also with "linux-image-2.6-686-smp".
If i try to remove the package, rather than purge, all seems to work
well and this is the output:
----------------------
(Reading database ... 80461 files and directories currently installed.)
Removing linux-image-2.6-386 ...
Removing linux-image-2.6.14-2-386 ...
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.14-2-686
Found kernel: /boot/vmlinuz-2.6.12-1-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 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 lilo
Press return to continue.
----------------------
I have seen bug #343093, but doesn't seem the same: here purge return an
error instead of a lock.
Some information about my system:
- Debian Sid
- linux-image-2.6.14-2-686 (2.6.14-6)
- yaird (0.0.12-1)
- initrd-tools (0.1.84)
- grub (0.97-2)
- libc6 (2.3.5-9)
Message-ID: <email address hidden>
Date: Sun, 25 Dec 2005 22:57:12 +0100
From: Cesare Leonardi <email address hidden>
To: <email address hidden>
Subject: Lock during kernel 2.6.14 purge
Package: linux-image-2.6-386
Version: 2.6.14-6
Trying to purge that package you get the following situation (purge
launched from aptitude):
------- ------- ------- - 2.6.14- 2-386 ... 2.6.14- 2-686 2.6.12- 1-686
(Reading database ... 80461 files and directories currently installed.)
Removing linux-image-2.6-386 ...
Removing linux-image-
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Updating /boot/grub/menu.lst ... done
The link /vmlinuz is a damaged link 2.6.14- 2-386 ... 2.6.14- 2-686 2.6.12- 1-686 ------- ------- -
Removing symbolic link vmlinuz
Unless you used the optional flag in lilo,
you may need to re-run 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 lilo
Purging configuration files for linux-image-
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
Updating /boot/grub/menu.lst ... done
-------
At that point the purging procedure seems locked (i have waited over a
minute) and i have to press CTRL+C. Then the output is:
------- ------- ------- - 2.6.14- 2-386 (--purge): image-2. 6.14-2- 386 ------- ------- -
dpkg: error processing linux-image-
subprocess post-removal script killed by signal (Interrupt)
Errors were encountered while processing:
linux-
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.
-------
I have verified such behaviour also with "linux- image-2. 6-686-smp" .
If i try to remove the package, rather than purge, all seems to work
well and this is the output:
------- ------- ------- - 2.6.14- 2-386 ... 2.6.14- 2-686 2.6.12- 1-686
(Reading database ... 80461 files and directories currently installed.)
Removing linux-image-2.6-386 ...
Removing linux-image-
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-
Found kernel: /boot/vmlinuz-
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 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 lilo
Press return to continue.
-------
I have seen bug #343093, but doesn't seem the same: here purge return an
error instead of a lock.
Some information about my system: 2.6.14- 2-686 (2.6.14-6)
- Debian Sid
- linux-image-
- yaird (0.0.12-1)
- initrd-tools (0.1.84)
- grub (0.97-2)
- libc6 (2.3.5-9)
Cesare.