linux-image configuration fails

[Debian Bug Importer]

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

[Jurij Smakov (jurij)]

retitle 343092 linux-image configuration fails
thanks

Hi,

This is a kernel-package bug, fixed in version 10.018. From the changelog:

kernel-package (10.018) unstable; urgency=low
[..]
   * When done with debconf, call stop: this shall help prevent errors if
     the hook scripts write to stdout. Also, when calling the hook scripts,
     redirect stdout to stderr, just in case -- and to ensure that the
     messages do not silently disappear.

I'm pretty sure that in your case the failure to configure is due to the
grub-update script writing to stdout, which was misinterpreted by debconf.
I'll keep the bug open to avoid duplicates and will close it as soon as
the new linux-image packages built with the fixed kernel-package are
uploaded.

Best regards,

Jurij Smakov <email address hidden>
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC

[Jean-Marc Ranger (ff942)]

Would anyone be kind enough to provide recovery instructions for this
issue, for current state and/or when the newer linux-image are
available? Link to an appropriate man page qualify :)

Thanks,

Jean-Marc

[Sven Luther (sven-luther)]

Hi Jean-Marc,

Can you please confirm that this issue should be closed, so that we can close
the bug report ?

Jurij said the bug was fixed in k-p 10.018, and both 2.6.14-7 and 2.6.15-1
where built with a more recent version of it.

Friendly,

Sven Luther

[maximilian attems (maks-debian)]

reopen 343092
reassign 343092 grub
stop

grub needs to be debconfied to allow latest linux-images to install.
at least update-grub needs to write to stderr.
better control would use the debconf ENV var to check context.

--
maks

[maximilian attems (maks-debian)]

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343092 yaird

[Debian Bug Importer (debzilla)]

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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 12 Dec 2005 18:09:10 +0200
From: Juhapekka Tolvanen <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Do not configure

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: serious

Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages have been kept back:
  adplay dar extract gnome-cups-manager pstoedit sidplay
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up linux-image-2.6.14-2-686 (2.6.14-5) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.14-4 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.14-4 was configured last, according to dpkg)
Running postinst hook.
Searching for GRUB installation directory ... found: /boot/grub
dpkg: error processing linux-image-2.6.14-2-686 (--configure):
 subprocess post-installation script returned error exit status 128
dpkg: dependency problems prevent configuration of linux-image-2.6-686:
 linux-image-2.6-686 depends on linux-image-2.6.14-2-686; however:
  Package linux-image-2.6.14-2-686 is not configured yet.
dpkg: error processing linux-image-2.6-686 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.14-2-686
 linux-image-2.6-686

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (101, 'testing'), (99, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=fi_FI@euro, LC_CTYPE=fi_FI@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii module-init-tools 3.2.2-1 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-1 Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn libc6-i686 <none> (no description available)

-- debconf information:
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:
* linux-image-2.6.14-2-686/prein...

[Debian Bug Importer (debzilla)]

Message-ID: <Pine.LNX.4.63.0512152034470.3875@bobcat>
Date: Thu, 15 Dec 2005 20:39:44 -0800 (PST)
From: Jurij Smakov <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Do not configure

retitle 343092 linux-image configuration fails
thanks

Hi,

This is a kernel-package bug, fixed in version 10.018. From the changelog:

kernel-package (10.018) unstable; urgency=low
[..]
   * When done with debconf, call stop: this shall help prevent errors if
     the hook scripts write to stdout. Also, when calling the hook scripts,
     redirect stdout to stderr, just in case -- and to ensure that the
     messages do not silently disappear.

I'm pretty sure that in your case the failure to configure is due to the
grub-update script writing to stdout, which was misinterpreted by debconf.
I'll keep the bug open to avoid duplicates and will close it as soon as
the new linux-image packages built with the fixed kernel-package are
uploaded.

Best regards,

Jurij Smakov <email address hidden>
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 16 Dec 2005 18:37:19 -0500
From: Jean-Marc Ranger <email address hidden>
To: <email address hidden>
Subject: recovery ?

Would anyone be kind enough to provide recovery instructions for this
issue, for current state and/or when the newer linux-image are
available? Link to an appropriate man page qualify :)

Thanks,

Jean-Marc

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 3 Jan 2006 15:02:49 +0100
From: Sven Luther <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1, ...

Hi Jean-Marc,

Can you please confirm that this issue should be closed, so that we can close
the bug report ?

Jurij said the bug was fixed in k-p 10.018, and both 2.6.14-7 and 2.6.15-1
where built with a more recent version of it.

Friendly,

Sven Luther

[Debian Bug Importer (debzilla)]

Message-ID: <20060103151036.GA4474@nancy>
Date: Tue, 3 Jan 2006 16:10:37 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: linux-image configuration fails

reopen 343092
reassign 343092 grub
stop

grub needs to be debconfied to allow latest linux-images to install.
at least update-grub needs to write to stderr.
better control would use the debconf ENV var to check context.

--
maks

[Debian Bug Importer (debzilla)]

Message-Id: <E1EtoUs-0001n7-7F@nancy>
Date: Tue, 3 Jan 2006 16:54:50 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: reassign 343092 to yaird

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343092 yaird

[Jonas Smedegaard (dr)]

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

reassign 343092 grub
thanks

On Tue, 3 Jan 2006 17:31:34 +0100
Maximilian Attems <email address hidden> wrote:

> On Tue, Jan 03, 2006 at 05:27:09PM +0100, Jonas Smedegaard wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Tue, 03 Jan 2006 08:03:14 -0800
> > <email address hidden> (Debian Bug Tracking System) wrote:
> >
> > > Processing commands for <email address hidden>:
> > >
> > > > # Automatically generated email from bts, devscripts version
> > > > # 2.9.10
> > > > reassign 343092 yaird
> > > Bug#343092: linux-image configuration fails
> > > Bug reassigned from package `grub' to `yaird'.
> >
> > Why?
> >
> > This bug seems unrelated to yaird and very much related to GRUB...
>
> was an error and promptly reassigned already,
> sorry for the noise.

It was not, but with this message it is being reassigned.

Please check if you then incorrectly reassigned some other bug to grub
instead...

 - Jonas

- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: [phone] Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDut03n7DbMsAkQLgRAhEQAKCVA6kCZm2JPIyzc1rDyBm52BrpHgCeKY5W
+tWHogIPuzQThISROuJW2QQ=
=Spfn
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 3 Jan 2006 21:23:19 +0100
From: Jonas Smedegaard <email address hidden>
To: Maximilian Attems <email address hidden>, <email address hidden>
Cc: <email address hidden>,
 <email address hidden>
Subject: Re: [Yaird-devel] Processed: reassign 343092 to yaird

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

reassign 343092 grub
thanks

On Tue, 3 Jan 2006 17:31:34 +0100
Maximilian Attems <email address hidden> wrote:

> On Tue, Jan 03, 2006 at 05:27:09PM +0100, Jonas Smedegaard wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >=20
> > On Tue, 03 Jan 2006 08:03:14 -0800
> > <email address hidden> (Debian Bug Tracking System) wrote:
> >=20
> > > Processing commands for <email address hidden>:
> > >=20
> > > > # Automatically generated email from bts, devscripts version
> > > > # 2.9.10
> > > > reassign 343092 yaird
> > > Bug#343092: linux-image configuration fails
> > > Bug reassigned from package `grub' to `yaird'.
> >=20
> > Why?
> >=20
> > This bug seems unrelated to yaird and very much related to GRUB...
>=20
> was an error and promptly reassigned already,
> sorry for the noise.

It was not, but with this message it is being reassigned.

Please check if you then incorrectly reassigned some other bug to grub
instead...

 - Jonas

- --=20
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: [phone] Website: http://dr.jones.dk/

 - Enden er n=E6r: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDut03n7DbMsAkQLgRAhEQAKCVA6kCZm2JPIyzc1rDyBm52BrpHgCeKY5W
+tWHogIPuzQThISROuJW2QQ=3D
=3DSpfn
-----END PGP SIGNATURE-----

[Jean-Marc Ranger (ff942)]

Sven Luther wrote:
 > Can you please confirm that this issue should be closed, so that we
 > can close the bug report ?

Hi Sven,

Confirmed. No longer visible on my side.

However, I can't confirm what exactly fixed it, but in the last days
before Christmas IIRC, 2.6.14-5 finally purged correctly.

Just upgraded today from 2.6.14-6 to -7 without problem.

(I'd still be interessed in hints on how to recover from this kind of
problem, and/or hints on how to rollback to prior version of a package,
but this is now way off-topic.)

Jean-Marc

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Message-ID: <email address hidden>
Date: Tue, 03 Jan 2006 22:35:08 -0500
From: Jean-Marc Ranger <email address hidden>
To: Sven Luther <email address hidden>
CC: <email address hidden>
Subject: Re: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1,
 ...

Sven Luther wrote:
 > Can you please confirm that this issue should be closed, so that we
 > can close the bug report ?

Hi Sven,

Confirmed. No longer visible on my side.

However, I can't confirm what exactly fixed it, but in the last days
before Christmas IIRC, 2.6.14-5 finally purged correctly.

Just upgraded today from 2.6.14-6 to -7 without problem.

(I'd still be interessed in hints on how to recover from this kind of
problem, and/or hints on how to rollback to prior version of a package,
but this is now way off-topic.)

Jean-Marc

[Sven Luther (sven-luther)]

On Tue, Jan 03, 2006 at 10:35:08PM -0500, Jean-Marc Ranger wrote:
> Sven Luther wrote:
> > Can you please confirm that this issue should be closed, so that we
> > can close the bug report ?
>
> Hi Sven,
>
> Confirmed. No longer visible on my side.
>
> However, I can't confirm what exactly fixed it, but in the last days
> before Christmas IIRC, 2.6.14-5 finally purged correctly.
>
> Just upgraded today from 2.6.14-6 to -7 without problem.

Cool, closing this bug report then.

> (I'd still be interessed in hints on how to recover from this kind of
> problem, and/or hints on how to rollback to prior version of a package,
> but this is now way off-topic.)

well, this is a tricky issue, and needs some playing with the installation
scripts, which can be found in both /var/lib/dpkg/info/<package>.* and
/etc/kernel/* for the kernel packages. Thos scripts may do important things,
or they may not, so just putting an exit 0 at the start of them may be a
solution or it may not, you would need to look at the individual scripts to
decide, especially since it may hose the system in a worse manner if not done
right.

Another trick is copying over the scripts that fail from an older or newer
version of the package.

In any case, it has to be a cautious and informed process, and i believe this
kind of bugs are the worse.

Friendly,

Sven Luther

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 4 Jan 2006 08:10:10 +0100
From: Sven Luther <email address hidden>
To: Jean-Marc Ranger <email address hidden>
Cc: Sven Luther <email address hidden>, <email address hidden>
Subject: Re: This bug should be fixed with both 2.6.14-7 and upcoming 2.6.15-1, ...

On Tue, Jan 03, 2006 at 10:35:08PM -0500, Jean-Marc Ranger wrote:
> Sven Luther wrote:
> > Can you please confirm that this issue should be closed, so that we
> > can close the bug report ?
>
> Hi Sven,
>
> Confirmed. No longer visible on my side.
>
> However, I can't confirm what exactly fixed it, but in the last days
> before Christmas IIRC, 2.6.14-5 finally purged correctly.
>
> Just upgraded today from 2.6.14-6 to -7 without problem.

Cool, closing this bug report then.

> (I'd still be interessed in hints on how to recover from this kind of
> problem, and/or hints on how to rollback to prior version of a package,
> but this is now way off-topic.)

well, this is a tricky issue, and needs some playing with the installation
scripts, which can be found in both /var/lib/dpkg/info/<package>.* and
/etc/kernel/* for the kernel packages. Thos scripts may do important things,
or they may not, so just putting an exit 0 at the start of them may be a
solution or it may not, you would need to look at the individual scripts to
decide, especially since it may hose the system in a worse manner if not done
right.

Another trick is copying over the scripts that fail from an older or newer
version of the package.

In any case, it has to be a cautious and informed process, and i believe this
kind of bugs are the worse.

Friendly,

Sven Luther

[Chuck Short (zulcss)]

Not us

[po Shapendonk (po-shapendonk)]

There is still more to it.

AN ALLE FINANZINVESTOREN!
DIESE AKTIE WIRD DURCHSTARTEN!
FREITAG 20. APRIL STARTET DIE HAUSSE!
REALISIERTER KURSGEWINN VON 400%+ IN 5 TAGEN!

Symbol: G7Q.F
Company: COUNTY LINE ENERGY
5 Tages Kursziel: 0.95
Schlusskurs: 0.21
WKN: A0J3B0
ISIN: US2224791077
Markt: Frankfurt

LASSEN SIE SICH DIESE CHANCE NICHT ENTGEHEN!
G7Q WIRD WIE EINE RAKETE DURCHSTARTEN!
UNSERE ERWARTUNGEN WIRD G7Q.F UBERTREFFEN!

This gives a generic interface to the device info and operations to both the tape and pcmcia devices.