grub - grub-install writes to stdout

[Debian Bug Importer]

Automatically imported from Debian bug report #344767 http://bugs.debian.org/344767

[Cesare Leonardi (celeonar)]

Cesare Leonardi wrote:
> Package: linux-image-2.6-386
> Version: 2.6.14-6

Same with linux-image-2.6-386 version 2.6.14-7: if i try to install also
the 386 image (side by side to the main linux-image-2.6-686), then i try
to remove it, the removal procedure hangs as described in the initial
message and i have to press CTRL+C to terminate it.

> 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)

 From the initial post, the only thing changed in this list is yaird,
now 0.0.12-3.

Cesare.

[Bernhard R. Link (brlink)]

I've the same behaviour here with the linux-image-2.6.14-2-sparc64,
everything works but when purging it hangs.

Adding some "print STDERR" into the postrm, it hangs in the
line
my $ret = purge();

Hochachtungsvoll,
 Bernhard R. Link

[Cesare Leonardi (celeonar)]

Cesare Leonardi wrote:
> I haven't tested 2.6.15 because it isn't available in my mirror yet. But
> the Nathanael posts tell us that the problem is still present in the
> latest kernel.
> As soon as it will be available on the mirror i use, i'll test 2.6.15.

Ok, 2.6.15 is arrived.
I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
to purge it and the operation failed. But now, it doesn't hang as stated
in the bug reports, but fails with an error:

(Reading database ... 83162 files and directories currently installed.)
Removing linux-image-2.6.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
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.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.15-1-486 (--purge):
  subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
  linux-image-2.6.15-1-486
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.

But since the "486" flavour is a new entry, i've also tryed
linux-image-2.6.15-1-686-smp, which i know was failing during purge
(while i was investigating for bug #344767, i had also tested
linux-image-2.6.14-2-686-smp (2.6.14-6), and it hanged like the others):
the purge operation for 2.6.15-686-smp failed like 486 flavour:

(Reading database ... 83105 files and directories currently installed.)
Removing linux-image-2.6.15-1-686-smp ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
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.15-1-686-smp ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.15-1-686-smp (--purge):
  subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
  linux-image-2.6.15-1-686-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.

Some information about my system:
- Debian Sid
- linux-image-2.6.15-1-686 (2.6.15-1)
- yaird (0.0.12-3)
- initrd-tools (0.1.84)
- grub (0.97-2)
- libc6 (2.3.5-11)
- libc6-i686 (2.3.5-11)

Regards.

Cesare.

[Sven Luther (sven-luther)]

reassign 344767 grub
thanks
On Thu, Jan 05, 2006 at 01:19:17AM +0100, Cesare Leonardi wrote:
> Sven Luther wrote:
> >It would be great if you could confirm the exact version of those two
> >packages, and could provide us some log of what is happening, as this bug
> >report doesn't seem to be very informative.
>
> For me, i have provided information in bug #344767, as i explained in
> the previous message: versions, logs, ecc.

I have now looked at this bug report, and it is indeed probable that it is a
bug in grub, who wants to write to stdout, which plays hell with the new
kernel-package debconfified due to messing up the debconf protocol.

Since policy mandates debconf for interaction, this is a RC grub bug, and a
proposed fix is have grub-updates output info on stderr instead.

There were some bugs we redirected to the grub guys, but i can't find them in
the BTS anymore, so reasigning the 344767 bug report to them.

Friendly,

Sven Luther

[Sven Luther (sven-luther)]

On Thu, Jan 05, 2006 at 03:51:54AM +0100, Cesare Leonardi wrote:
> Cesare Leonardi wrote:
> >I haven't tested 2.6.15 because it isn't available in my mirror yet. But
> >the Nathanael posts tell us that the problem is still present in the
> >latest kernel.
> >As soon as it will be available on the mirror i use, i'll test 2.6.15.
>
> Ok, 2.6.15 is arrived.
> I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
> to purge it and the operation failed. But now, it doesn't hang as stated
> in the bug reports, but fails with an error:

Indeed, this is a grub RC bug, which need to fix their grub-update call from
/etc/kernel/*.d/grub or whatever scripts.

Friendly,

Sven Luther

[Bastian Blank (waldi)]

# Automatically generated email from bts, devscripts version 2.9.10
severity 344767 grave

[Bastian Blank (waldi)]

# Automatically generated email from bts, devscripts version 2.9.10
retitle 344767 grub - grub-install writes to stdout

[Otavio Salvador (otavio)]

# Automatically generated email from bts, devscripts version 2.9.10
package grub grub-disk grub-doc
tags 344767 + pending

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #344767 http://bugs.debian.org/344767

[Debian Bug Importer (debzilla)]

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-to...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 31 Dec 2005 01:02:06 +0100
From: Cesare Leonardi <email address hidden>
To: <email address hidden>
Subject: Re: Bug#344767: Lock during kernel 2.6.14 purge

Cesare Leonardi wrote:
> Package: linux-image-2.6-386
> Version: 2.6.14-6

Same with linux-image-2.6-386 version 2.6.14-7: if i try to install also
the 386 image (side by side to the main linux-image-2.6-686), then i try
to remove it, the removal procedure hangs as described in the initial
message and i have to press CTRL+C to terminate it.

> 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)

 From the initial post, the only thing changed in this list is yaird,
now 0.0.12-3.

Cesare.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 31 Dec 2005 13:23:22 +0100
From: "Bernhard R. Link" <email address hidden>
To: <email address hidden>
Subject: same here with linux-image-2.6.14-2-sparc64

I've the same behaviour here with the linux-image-2.6.14-2-sparc64,
everything works but when purging it hangs.

Adding some "print STDERR" into the postrm, it hangs in the
line
my $ret = purge();

Hochachtungsvoll,
 Bernhard R. Link

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 05 Jan 2006 03:51:54 +0100
From: Cesare Leonardi <email address hidden>
To: Sven Luther <email address hidden>
CC: <email address hidden>, Nathanael Nerode <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: Bug#346028: linux-2.6: Hangs while attempting to purge

Cesare Leonardi wrote:
> I haven't tested 2.6.15 because it isn't available in my mirror yet. But
> the Nathanael posts tell us that the problem is still present in the
> latest kernel.
> As soon as it will be available on the mirror i use, i'll test 2.6.15.

Ok, 2.6.15 is arrived.
I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
to purge it and the operation failed. But now, it doesn't hang as stated
in the bug reports, but fails with an error:

(Reading database ... 83162 files and directories currently installed.)
Removing linux-image-2.6.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
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.15-1-486 ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.15-1-486 (--purge):
  subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
  linux-image-2.6.15-1-486
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.

But since the "486" flavour is a new entry, i've also tryed
linux-image-2.6.15-1-686-smp, which i know was failing during purge
(while i was investigating for bug #344767, i had also tested
linux-image-2.6.14-2-686-smp (2.6.14-6), and it hanged like the others):
the purge operation for 2.6.15-686-smp failed like 486 flavour:

(Reading database ... 83105 files and directories currently installed.)
Removing linux-image-2.6.15-1-686-smp ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
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.15-1-686-smp ...
Running postrm hook /sbin/update-grub .
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.15-1-686-smp (--purge):
  subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
  linux-image-2.6.15-1-686-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.

Some information about my system:
- Debian Sid
-...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 07:59:22 +0100
From: Sven Luther <email address hidden>
To: Cesare Leonardi <email address hidden>
Cc: Sven Luther <email address hidden>, <email address hidden>,
 Nathanael Nerode <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#346028: linux-2.6: Hangs while attempting to purge

On Thu, Jan 05, 2006 at 03:51:54AM +0100, Cesare Leonardi wrote:
> Cesare Leonardi wrote:
> >I haven't tested 2.6.15 because it isn't available in my mirror yet. But
> >the Nathanael posts tell us that the problem is still present in the
> >latest kernel.
> >As soon as it will be available on the mirror i use, i'll test 2.6.15.
>
> Ok, 2.6.15 is arrived.
> I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
> to purge it and the operation failed. But now, it doesn't hang as stated
> in the bug reports, but fails with an error:

Indeed, this is a grub RC bug, which need to fix their grub-update call from
/etc/kernel/*.d/grub or whatever scripts.

Friendly,

Sven Luther

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 07:57:40 +0100
From: Sven Luther <email address hidden>
To: Cesare Leonardi <email address hidden>, <email address hidden>
Cc: Sven Luther <email address hidden>, <email address hidden>,
 Nathanael Nerode <email address hidden>, <email address hidden>
Subject: Re: Bug#346028: linux-2.6: Hangs while attempting to purge

reassign 344767 grub
thanks
On Thu, Jan 05, 2006 at 01:19:17AM +0100, Cesare Leonardi wrote:
> Sven Luther wrote:
> >It would be great if you could confirm the exact version of those two
> >packages, and could provide us some log of what is happening, as this bug
> >report doesn't seem to be very informative.
>
> For me, i have provided information in bug #344767, as i explained in
> the previous message: versions, logs, ecc.

I have now looked at this bug report, and it is indeed probable that it is a
bug in grub, who wants to write to stdout, which plays hell with the new
kernel-package debconfified due to messing up the debconf protocol.

Since policy mandates debconf for interaction, this is a RC grub bug, and a
proposed fix is have grub-updates output info on stderr instead.

There were some bugs we redirected to the grub guys, but i can't find them in
the BTS anymore, so reasigning the 344767 bug report to them.

Friendly,

Sven Luther

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Thu, 5 Jan 2006 12:21:52 +0100
From: Bastian Blank <email address hidden>
To: <email address hidden>
Subject: severity of 344767 is grave

# Automatically generated email from bts, devscripts version 2.9.10
severity 344767 grave

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Thu, 5 Jan 2006 12:23:09 +0100
From: Bastian Blank <email address hidden>
To: <email address hidden>
Subject: retitle 344767 to grub - grub-install writes to stdout

# Automatically generated email from bts, devscripts version 2.9.10
retitle 344767 grub - grub-install writes to stdout

[Bastian Blank (waldi)]

tags 344739 patch
tags 344767 patch
--
Earth -- mother of the most beautiful women in the universe.
  -- Apollo, "Who Mourns for Adonais?" stardate 3468.1

[Debian Bug Importer (debzilla)]

Message-Id: <20060105115509.67C361C0B6AF@localhost>
Date: Thu, 5 Jan 2006 09:55:09 -0200
From: Otavio Salvador <email address hidden>
To: <email address hidden>
Subject: setting package to grub grub-disk grub-doc, tagging 344767

# Automatically generated email from bts, devscripts version 2.9.10
package grub grub-disk grub-doc
tags 344767 + pending

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 13:05:59 +0100
From: Bastian Blank <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: patch

--3uo+9/B/ebqu+fSQ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline

tags 344739 patch
tags 344767 patch
--
Earth -- mother of the most beautiful women in the universe.
  -- Apollo, "Who Mourns for Adonais?" stardate 3468.1

--3uo+9/B/ebqu+fSQ
Content-Type: text/plain; charset=utf-8
Content-Disposition: attachment; filename=diff

diff -u grub-0.97/debian/update-grub grub-0.97/debian/update-grub
--- grub-0.97/debian/update-grub
+++ grub-0.97/debian/update-grub
@@ -591,28 +591,28 @@
 }

-echo -n "Testing for an existing GRUB menu.list file ... "
+echo -n "Testing for an existing GRUB menu.list file ... " >&2

 # Test if our menu file exists
 if [ -f "$menu_file" ] ; then
  menu="$menu_file"
  rm -f $newtemplate
  unset newtemplate
- echo "found: $menu_file"
+ echo "found: $menu_file" >&2
  cp -f "$menu_file" "$menu_file~"
 else
  # if not ask user if they want us to create one
  menu="$menu_file"
- echo
- echo
- echo -n "Could not find $menu_file file. "
+ echo >&2
+ echo >&2
+ echo -n "Could not find $menu_file file. " >&2
  if [ "-y" = "$command_line_arguments" ] ; then
- echo
- echo "Generating $menu_file"
+ echo >&2
+ echo "Generating $menu_file" >&2
   answer=y
  else
- echo -n "Would you like $menu_file generated for you? "
- echo -n "(y/N) "
+ echo -n "Would you like $menu_file generated for you? " >&2
+ echo -n "(y/N) " >&2
   read answer
  fi

@@ -737,23 +737,23 @@
 echo "## ## End Default Options ##" >> $buffer
 echo >> $buffer

-echo -n "Searching for splash image ... "
+echo -n "Searching for splash image ... " >&2
 current_splash=`grep '^splashimage=' ${grub_dir}/menu.lst || true`
 splashimage_path="splashimage=${grub_root_device}${grub_dir##${boot_device:+/boot}}/splash.xpm.gz"
 if [ -f "${grub_dir}/splash.xpm.gz" ] && [ "$current_splash" = "" ]; then
- echo "found: /boot/grub/splash.xpm.gz"
+ echo "found: /boot/grub/splash.xpm.gz" >&2
        echo "$splashimage_path" >> $buffer
        echo >> $buffer
 elif [ -f "${grub_dir}/splash.xpm.gz" ] && [ "$current_splash" = "$splashimage_path" ]; then
- echo "found: /boot/grub/splash.xpm.gz"
+ echo "found: /boot/grub/splash.xpm.gz" >&2
        echo "$splashimage_path" >> $buffer
        echo >> $buffer
 elif [ "$current_splash" != "" ] && [ "$current_splash" != "$splashimage_path" ]; then
- echo "found but preserving previous setting: $(grep '^splashimage=' /boot/grub/menu.lst)"
+ echo "found but preserving previous setting: $(grep '^splashimage=' /boot/grub/menu.lst)" >&2
        echo "$current_splash" >> $buffer
        echo >> $buffer
 else
- echo "none found, skipping ..."
+ echo "none found, skipping ..." >&2
 fi

 sortedKernels=""
@@ -808,7 +808,7 @@
   initrd=$kernel_dir/$initrdName
  fi

- echo "Found kernel: $kernel"
+ echo "Found kernel: $kernel" >&2

  if [ "$kernelName" = "vmlinuz" ]; then
   if [ -L "/boot/$kernelName" ]; then
@@ -860,7 +860,7 @@
    currentOpt=
    initrd=

- echo "Fo...

[Cesare Leonardi (celeonar)]

Sven Luther wrote:
>>Ok, 2.6.15 is arrived.
>>I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
>>to purge it and the operation failed. But now, it doesn't hang as stated
>>in the bug reports, but fails with an error:
>
>
> Indeed, this is a grub RC bug, which need to fix their grub-update call from
> /etc/kernel/*.d/grub or whatever scripts.

Ok, i have also read the other your mails regards the grub bug.
But i would inform you that the /etc/kernel/ folder (that you have
requested us to post in the previous messages) doesn't exist on my system...

Regards.

Cesare.

[Sven Luther (sven-luther)]

On Fri, Jan 06, 2006 at 01:32:13AM +0100, Cesare Leonardi wrote:
> Sven Luther wrote:
> >>Ok, 2.6.15 is arrived.
> >>I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
> >>to purge it and the operation failed. But now, it doesn't hang as stated
> >>in the bug reports, but fails with an error:
> >
> >
> >Indeed, this is a grub RC bug, which need to fix their grub-update call
> >from
> >/etc/kernel/*.d/grub or whatever scripts.
>
> Ok, i have also read the other your mails regards the grub bug.
> But i would inform you that the /etc/kernel/ folder (that you have
> requested us to post in the previous messages) doesn't exist on my system...

Mmm, then i am out of my depth, and i think it is best you follow up with
Manoj, since it is a kernel-package issue.

Friendly,

Sven Luther

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 06 Jan 2006 01:32:13 +0100
From: Cesare Leonardi <email address hidden>
To: Sven Luther <email address hidden>
CC: <email address hidden>, Nathanael Nerode <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: Bug#346028: linux-2.6: Hangs while attempting to purge

Sven Luther wrote:
>>Ok, 2.6.15 is arrived.
>>I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
>>to purge it and the operation failed. But now, it doesn't hang as stated
>>in the bug reports, but fails with an error:
>
>
> Indeed, this is a grub RC bug, which need to fix their grub-update call from
> /etc/kernel/*.d/grub or whatever scripts.

Ok, i have also read the other your mails regards the grub bug.
But i would inform you that the /etc/kernel/ folder (that you have
requested us to post in the previous messages) doesn't exist on my system...

Regards.

Cesare.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 01:38:27 +0100
From: Sven Luther <email address hidden>
To: Cesare Leonardi <email address hidden>
Cc: Sven Luther <email address hidden>, <email address hidden>,
 Nathanael Nerode <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#346028: linux-2.6: Hangs while attempting to purge

On Fri, Jan 06, 2006 at 01:32:13AM +0100, Cesare Leonardi wrote:
> Sven Luther wrote:
> >>Ok, 2.6.15 is arrived.
> >>I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
> >>to purge it and the operation failed. But now, it doesn't hang as stated
> >>in the bug reports, but fails with an error:
> >
> >
> >Indeed, this is a grub RC bug, which need to fix their grub-update call
> >from
> >/etc/kernel/*.d/grub or whatever scripts.
>
> Ok, i have also read the other your mails regards the grub bug.
> But i would inform you that the /etc/kernel/ folder (that you have
> requested us to post in the previous messages) doesn't exist on my system...

Mmm, then i am out of my depth, and i think it is best you follow up with
Manoj, since it is a kernel-package issue.

Friendly,

Sven Luther

[Otavio Salvador (otavio)]

Sven Luther <email address hidden> writes:

> Mmm, then i am out of my depth, and i think it is best you follow up with
> Manoj, since it is a kernel-package issue.

I and Bastian did the fix for it. It should be include today.

--
        O T A V I O S A L V A D O R
---------------------------------------------
 E-mail: <email address hidden> UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 06 Jan 2006 09:12:41 -0200
From: Otavio Salvador <email address hidden>
To: Sven Luther <email address hidden>
Cc: <email address hidden>, Cesare Leonardi <email address hidden>,
 Nathanael Nerode <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#344767: Bug#346028: linux-2.6: Hangs while attempting to purge

Sven Luther <email address hidden> writes:

> Mmm, then i am out of my depth, and i think it is best you follow up with
> Manoj, since it is a kernel-package issue.

I and Bastian did the fix for it. It should be include today.

--
        O T A V I O S A L V A D O R
---------------------------------------------
 E-mail: <email address hidden> UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

[Otavio Salvador (otavio)]

Source: grub
Source-Version: 0.97-3

We believe that the bug you reported is fixed in the latest version of
grub, which is due to be installed in the Debian FTP archive:

grub-disk_0.97-3_all.deb
  to pool/main/g/grub/grub-disk_0.97-3_all.deb
grub-doc_0.97-3_all.deb
  to pool/main/g/grub/grub-doc_0.97-3_all.deb
grub_0.97-3.diff.gz
  to pool/main/g/grub/grub_0.97-3.diff.gz
grub_0.97-3.dsc
  to pool/main/g/grub/grub_0.97-3.dsc
grub_0.97-3_i386.deb
  to pool/main/g/grub/grub_0.97-3_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otavio Salvador <email address hidden> (supplier of updated grub package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 9 Jan 2006 13:37:41 -0200
Source: grub
Binary: grub-disk grub grub-doc
Architecture: source i386 all
Version: 0.97-3
Distribution: unstable
Urgency: low
Maintainer: Grub Maintainers <email address hidden>
Changed-By: Otavio Salvador <email address hidden>
Description:
 grub - GRand Unified Bootloader
 grub-disk - GRUB bootable disk image
 grub-doc - Documentation for GRand Unified Bootloader
Closes: 264312 314210 342221 344739 344767 346080 346127 346327
Changes:
 grub (0.97-3) unstable; urgency=low
 .
   * Replace automake1.9 build-dependencie with automake1.8 to fix a FTBFS
     issue. (closes: #344739, #346080)
   * Redirect output to stderr. Thanks Bastian Blank <email address hidden> for
     a better solution. (closes: #344767, #346327)
   * Add print_func.diff patch to beep in menu.lst. Useful for blind
     people. Really thank up Osvaldo La rosa <email address hidden> for the
     patch. (closes: #314210)
   * Applied patch provided by Kristian Edlund <email address hidden> to fix
     ordering kernel issues. (closes: #264312, #342221)
   * Applied patch provided by Michal Cihar <email address hidden> to allow
     update-grub to run with dash. (closes: #346127)
Files:
 f33f9d32562bf9a3a054473d9edf9309 932 admin optional grub_0.97-3.dsc
 ea9a96d60e9760f313ec04dc97316f20 60160 admin optional grub_0.97-3.diff.gz
 5ce5fdba383383e99616b9cc77ec7d9f 357734 admin optional grub_0.97-3_i386.deb
 f5f34c8713f72ab3883e9b30a27fe9b0 231474 admin optional grub-disk_0.97-3_all.deb
 a4440c379067ce3b2f1ca20bd8c54176 266292 doc optional grub-doc_0.97-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDwoRULqiZQEml+FURAqkHAJ9erPyIqxAyOEZ8YoYUDMa6ZFx+sACfTdbf
yFkKvkUX5l5tQk5MgcquQPI=
=h+iY
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 09 Jan 2006 07:47:03 -0800
From: Otavio Salvador <email address hidden>
To: <email address hidden>
Subject: Bug#344767: fixed in grub 0.97-3

Source: grub
Source-Version: 0.97-3

We believe that the bug you reported is fixed in the latest version of
grub, which is due to be installed in the Debian FTP archive:

grub-disk_0.97-3_all.deb
  to pool/main/g/grub/grub-disk_0.97-3_all.deb
grub-doc_0.97-3_all.deb
  to pool/main/g/grub/grub-doc_0.97-3_all.deb
grub_0.97-3.diff.gz
  to pool/main/g/grub/grub_0.97-3.diff.gz
grub_0.97-3.dsc
  to pool/main/g/grub/grub_0.97-3.dsc
grub_0.97-3_i386.deb
  to pool/main/g/grub/grub_0.97-3_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otavio Salvador <email address hidden> (supplier of updated grub package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 9 Jan 2006 13:37:41 -0200
Source: grub
Binary: grub-disk grub grub-doc
Architecture: source i386 all
Version: 0.97-3
Distribution: unstable
Urgency: low
Maintainer: Grub Maintainers <email address hidden>
Changed-By: Otavio Salvador <email address hidden>
Description:
 grub - GRand Unified Bootloader
 grub-disk - GRUB bootable disk image
 grub-doc - Documentation for GRand Unified Bootloader
Closes: 264312 314210 342221 344739 344767 346080 346127 346327
Changes:
 grub (0.97-3) unstable; urgency=low
 .
   * Replace automake1.9 build-dependencie with automake1.8 to fix a FTBFS
     issue. (closes: #344739, #346080)
   * Redirect output to stderr. Thanks Bastian Blank <email address hidden> for
     a better solution. (closes: #344767, #346327)
   * Add print_func.diff patch to beep in menu.lst. Useful for blind
     people. Really thank up Osvaldo La rosa <email address hidden> for the
     patch. (closes: #314210)
   * Applied patch provided by Kristian Edlund <email address hidden> to fix
     ordering kernel issues. (closes: #264312, #342221)
   * Applied patch provided by Michal Cihar <email address hidden> to allow
     update-grub to run with dash. (closes: #346127)
Files:
 f33f9d32562bf9a3a054473d9edf9309 932 admin optional grub_0.97-3.dsc
 ea9a96d60e9760f313ec04dc97316f20 60160 admin optional grub_0.97-3.diff.gz
 5ce5fdba383383e99616b9cc77ec7d9f 357734 admin optional grub_0.97-3_i386.deb
 f5f34c8713f72ab3883e9b30a27fe9b0 231474 admin optional grub-disk_0.97-3_all.deb
 a4440c379067ce3b2f1ca20bd8c54176 266292 doc optional grub-doc_0.97-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDwoRULqiZQEml+FURAqkHAJ9erPyIqxAyOEZ8YoYUDMa6ZFx+sACfTdbf
yFkKvkUX5l5tQk5MgcquQPI=
=h+iY
-----END PGP SIGNATURE-----

[Jean-Marc Ranger (ff942)]

Sorry to break the party, but the problem is still present. Kernel
2.6.14-7 and grub 0.97-3. Purge freeze just after update-grub completes.

In fact, I'm skeptical that this is a grub bug, since if I remove grub
prior to purging the kernel, it freezes too.

Let me know if anything else is needed or need to be tried. Or feel
free to ignore if 2.6.15 doesn't exhibit this behavior (I didn't try),
since 2.6.14-7 is history.

Jean-Marc

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Message-ID: <email address hidden>
Date: Thu, 12 Jan 2006 19:27:44 -0500
From: Jean-Marc Ranger <email address hidden>
To: <email address hidden>
CC: Sven Luther <email address hidden>
Subject: Re: Bug#344767: Lock during kernel 2.6.14 purge

Sorry to break the party, but the problem is still present. Kernel
2.6.14-7 and grub 0.97-3. Purge freeze just after update-grub completes.

In fact, I'm skeptical that this is a grub bug, since if I remove grub
prior to purging the kernel, it freezes too.

Let me know if anything else is needed or need to be tried. Or feel
free to ignore if 2.6.15 doesn't exhibit this behavior (I didn't try),
since 2.6.14-7 is history.

Jean-Marc

[Sven Luther (sven-luther)]

On Thu, Jan 12, 2006 at 07:27:44PM -0500, Jean-Marc Ranger wrote:
> Sorry to break the party, but the problem is still present. Kernel
> 2.6.14-7 and grub 0.97-3. Purge freeze just after update-grub completes.
>
> In fact, I'm skeptical that this is a grub bug, since if I remove grub
> prior to purging the kernel, it freezes too.

Does it also remove the grub hooks in /etc/kernel/* ? Those are the ones
causing the problem, i believe.

> Let me know if anything else is needed or need to be tried. Or feel
> free to ignore if 2.6.15 doesn't exhibit this behavior (I didn't try),
> since 2.6.14-7 is history.

Indeed, if 2.6.15 solves this problem, we can close this bug. But does it ?

Friendly,

Sven Luther

[Jean-Marc Ranger (ff942)]

> Does it also remove the grub hooks in /etc/kernel/* ? Those are the ones
> causing the problem, i believe.

The only reference I see to grub there is in kernel-img.conf.
Uninstalling grub (0.97-3) does not change that file, but delete the
/sbin/update-grub file that it refers to. Removing those references
changes nothing to my purge problem.

> Indeed, if 2.6.15 solves this problem, we can close this bug. But does it ?

Sorry for not trying that in the first place, but that's a test a little
too rough to run over dial-up :) I just tried, and 2.6.15 is OK.

So this one can be closed. My apologies for keeping it open unnecessarily.

Thanks for your help,

Jean-Marc

[Sven Luther (sven-luther)]

On Sat, Jan 14, 2006 at 01:15:22PM -0500, Jean-Marc Ranger wrote:
> >Does it also remove the grub hooks in /etc/kernel/* ? Those are the ones
> >causing the problem, i believe.
>
> The only reference I see to grub there is in kernel-img.conf.
> Uninstalling grub (0.97-3) does not change that file, but delete the
> /sbin/update-grub file that it refers to. Removing those references
> changes nothing to my purge problem.
>
> >Indeed, if 2.6.15 solves this problem, we can close this bug. But does it
> >?
>
> Sorry for not trying that in the first place, but that's a test a little
> too rough to run over dial-up :) I just tried, and 2.6.15 is OK.
>
> So this one can be closed. My apologies for keeping it open unnecessarily.

No problem, thanks for testing, will close this bug.

Friendly,

Sven Luther

[Edward C. Jones (edcjones)]

I use a PC with an AMD64 +3500 chip and Debian unstable, i386 port.

I had the problem described here which I reported as bug #349219. I have
grub 0.97-4. I still cannot purge "linux-image-2.6.14-2-386". Is bug
#344767 fixed in grub 0.97-4?

[Kristian Edlund (edlund)]

Yes I believe that he bug is fixed in the 0.97-3 release. I just tried
to install kernel 2.4.17-2-k7 and remove it again, and there was no
problems with the scripts running.

After that I purged the configuration, which also went without problems.

I have tested with 2.6.15 as well, which also runs without problems. So
I doubt that #349291, is related to this bug.

When you try to purge your kernel, what command are you using and what
happens?

--
Best Regards
Kristian Edlund

GPG ID: 7DD7559F

[Otavio Salvador (otavio)]

Kristian Edlund <email address hidden> writes:

> Yes I believe that he bug is fixed in the 0.97-3 release. I just tried
> to install kernel 2.4.17-2-k7 and remove it again, and there was no
> problems with the scripts running.
>
> After that I purged the configuration, which also went without problems.
>
> I have tested with 2.6.15 as well, which also runs without problems. So
> I doubt that #349291, is related to this bug.
>
> When you try to purge your kernel, what command are you using and what
> happens?

Yes, both bugs were in kernel-package in previous versions. Close it.

--
        O T A V I O S A L V A D O R
---------------------------------------------
 E-mail: <email address hidden> UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

[Otavio Salvador (otavio)]

"Edward C. Jones" <email address hidden> writes:

> I use a PC with an AMD64 +3500 chip and Debian unstable, i386 port.
>
> I had the problem described here which I reported as bug #349219. I
> have grub 0.97-4. I still cannot purge "linux-image-2.6.14-2-386". Is
> bug #344767 fixed in grub 0.97-4?

the problem isn't with grub but kernel-package scripts. Check the
postinst where it stops. Try to run it for purge with -x.

--
        O T A V I O S A L V A D O R
---------------------------------------------
 E-mail: <email address hidden> UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

[Otavio Salvador (otavio)]

Cesare Leonardi <email address hidden> writes:

> Hi Otavio.
> Recently i've talked with someone else that cannot purge 2.6.14, as
> described in #344767.
> I know that now it is solved for 2.6.15, but for people that still use
> 2.6.14 or have used it, the problem of purging it completely still
> exist. For example on my machine, the various kernel images i've used
> when i looked for bug 344767 are now uninstalled but marked as "c" and
> if i try to purge them, the locks described in the bug report arise.
> After upgrading to 2.6.15 and have seen that the bug was corrected,
> i've forgotten about this and the not clean situation left by the
> 2.6.14 uninstall procedure.

Edit its postrm file and remove db_stop call, IIRC. Should work.

--
        O T A V I O S A L V A D O R
---------------------------------------------
 E-mail: <email address hidden> UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

[Cesare Leonardi (celeonar)]

Hi Otavio.
Recently i've talked with someone else that cannot purge 2.6.14, as
described in #344767.
I know that now it is solved for 2.6.15, but for people that still use
2.6.14 or have used it, the problem of purging it completely still
exist. For example on my machine, the various kernel images i've used
when i looked for bug 344767 are now uninstalled but marked as "c" and
if i try to purge them, the locks described in the bug report arise.
After upgrading to 2.6.15 and have seen that the bug was corrected, i've
forgotten about this and the not clean situation left by the 2.6.14
uninstall procedure.

At the last comment of the bug report you have reported a method to
clean the situation that i haven't understand:

>> I had the problem described here which I reported as bug #349219. I
>> have grub 0.97-4. I still cannot purge "linux-image-2.6.14-2-386". Is
>> bug #344767 fixed in grub 0.97-4?
>
> the problem isn't with grub but kernel-package scripts. Check the
> postinst where it stops. Try to run it for purge with -x.

To which program do the "-x" options belong to?
Please, can you re-explain how to definitively purge 2.6.14 in a more
verbose way?

I've CC'ed this message to the bug report hoping that your reply will go
there too, helping other people that try to solve that purging problem.

Regards.

Cesare.

[Sam Morris (yrro)]

Cesare Leonardi wrote:
> Recently i've talked with someone else that cannot purge the 2.6.14
> kernel, due to bug #344767. It's a known problem, already solved for
> 2.6.15, but for people that still use 2.6.14 or have used it, the
> problem of purging it completely still exist.
> For example on my machine, the various kernel images i've installed in
> the past, are now uninstalled but marked as "c" and if i try to purge
> them, the lock described in the bug report arise. Then i have to press
> CTRL+C to exit.
 >
 > [snip]
>
> As suggested in the bug report, i've tryed to look at the postrm scripts
> in "/var/lib/dpkg/info/" but i cannot understand them adequately (i
> don't know perl).

You need to edit "/var/lib/dpkg/info/linux-image-2.6.14-2-k7.postrm".
Comment out line 268, which reads: "$ret = stop ();". Then purge the
package.

> Regards.
>
> Cesare.

PS - why do packages without any config files get into the config-files
state in the first place? :)

--
Sam Morris
http://robots.org.uk/

PGP key id 5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078

[Colin Watson (cjwatson)]

This doesn't affect Ubuntu; we haven't taken those kernel-package changes in Dapper, and I think we should be OK for dapper+1 now too.