Bug#601962: linux-image-2.6.32-5-amd64: removal fails in a clean chroot

[Lucas Nussbaum <lucas@lucas-nussbaum.net>]

severity 601962 important
thanks

On 31/10/10 at 15:58 +0100, Julien Cristau wrote:
> On Sun, Oct 31, 2010 at 12:46:55 +0100, Lucas Nussbaum wrote:
> 
> > Removing linux-image-2.6.32-5-amd64 in a clean chroot fails:
> > # apt-get remove --purge linux-image-2.6.32-5-amd64
> > Reading package lists... Done
> > Building dependency tree       
> > Reading state information... Done
> > The following packages will be REMOVED:
> >   linux-image-2.6.32-5-amd64*
> > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> > After this operation, 99.0 MB disk space will be freed.
> > Do you want to continue [Y/n]? 
> > (Reading database ... 9662 files and directories currently installed.)
> > Removing linux-image-2.6.32-5-amd64 ...
> > dpkg: error processing linux-image-2.6.32-5-amd64 (--purge):
> >  subprocess installed pre-removal script returned error exit status 1
> > configured to not write apport reports
> >                                       Errors were encountered while processing:
> >  linux-image-2.6.32-5-amd64
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> Any chance you can test that with set -x?

Not really, since it's perl;)

But I found out that the problem is that I get into the "$running eq
$version" test, but I use the debconf non-interactive frontend. So I
don't see the question about removing the running kernel image, but the
script exits with 1.

It would be nice to display an error message, like:
  if ($answer =~ /^(y|t)/i) {
+    print STDERR "Aborting the removal of the running kernel image.\n";
     exit 1; #Operation not permitted
  }
  else {
     print STDERR "Ok, proceeding with removing running kernel image.\n";
  }

- Lucas