Bug#602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb
Package: linux-image Version: 2.6.32-5-686_2.6.32-27_i386.deb Severity: normal Debian/Squueze - Linux 2.6.32-5-686 #1 SMP Sat Jul 24 02:27:10 UTC 2010 i686 GNU/Linux Hi all, last week the upgrading to sub '27' of captioned linux-image stopped on a line saying 'Running yes' while running update-initramfs. To continue, I had to find the relating process and kill it, thus receiving an error and no upgrading of the image. I tried a few times until, almost by chance, looking at the 'ps' output I saw this line: root 22526 0.0 0.0 3680 480 pts/2S+ 00:02 0:00 \_ yes 2.6.32-5-686 /boot/vmlinuz-2.6.32-5-686 thus becoming aware there really was a '/usr/bin/yes' program (in coreutils pkg). So I decided to try again after hijacking 'yes' (moving it to '/usr/bin/OLD.yes'): # apt-get upgrade Setting up linux-image-2.6.32-5-686 (2.6.32-27) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 initrd.img(/boot/initrd.img-2.6.32-5-686 ) points to /boot/initrd.img-2.6.32-5-686 (/boot/initrd.img-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 347. vmlinuz(/boot/vmlinuz-2.6.32-5-686 ) points to /boot/vmlinuz-2.6.32-5-686 (/boot/vmlinuz-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 347. Running yes. User postinst hook script [yes] failed to execute: No such file or directory ^ dpkg: error processing linux-image-2.6.32-5-686 (--configure): subprocess installed post-installation script returned error exit status 255 . Errors were encountered while processing: linux-image-2.6.32-5-686 ... E: Sub-process /usr/bin/dpkg returned an error code (1) Despite the error, the image is correctly created and the bootloader updated. However, looking into the 'postinst' file, I was unable to find a call to 'yes' so I do not quite understand what and why is happening. On the other hand, I see no reason why such a program, whose aim is to 'output a string repeatedly until killed' should intervene in the upgrading process. Thanks for any help. Regards, ennio -- [Perche' usare Win$ozz (dico io) se ...anche uno sciocco sa farlo.\\?// Fa' qualche cosa di cui non sei capace! (diceva Henry Miller) ](°|°) Ricevo solo messaggi Content-Type: plain/text (no html o multipart). )=( !!! -- e-mail a mio nome via OE (M$) sono false e infette -- !!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602940: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb)
* Debian Bug Tracking System ow...@bugs.debian.org [091110, 19:15]: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb It has been closed by Ben Hutchings b...@decadent.org.uk. [...] This is your configuration error. Remove the line 'postinst_hook = yes' from /etc/kernel-img.conf. Ben. Hi Ben, thank you very much indeed for the quick answer. I must have misunderstood the suggestion given in a previous update (Sept. 25th, 2010) about replacing the line 'do_bootloader = yes' with 'postinst_hook = yes', which I did simply as suggested, without touching anything else. Now, what triggers the /usr/bin/yes still remains a mistery to me. May be this program shoud be given a different name, provided it is worth keeping it ;-). Thanks againg, Ennio -- [Perche' usare Win$ozz (dico io) se ...anche uno sciocco sa farlo.\\?// Fa' qualche cosa di cui non sei capace! (diceva Henry Miller) ](°|°) Ricevo solo messaggi Content-Type: plain/text (no html o multipart). )=( !!! -- e-mail a mio nome via OE (M$) sono false e infette -- !!! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602940: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb)
On Tue, Nov 09, 2010 at 09:13:41PM +0100, ennio wrote: * Debian Bug Tracking System ow...@bugs.debian.org [091110, 19:15]: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb It has been closed by Ben Hutchings b...@decadent.org.uk. [...] This is your configuration error. Remove the line 'postinst_hook = yes' from /etc/kernel-img.conf. Ben. Hi Ben, thank you very much indeed for the quick answer. I must have misunderstood the suggestion given in a previous update (Sept. 25th, 2010) about replacing the line 'do_bootloader = yes' with 'postinst_hook = yes', which I did simply as suggested, without touching anything else. The actual message is: If the boot loader needs to be updated whenever a new kernel is installed, the boot loader package should install a script in /etc/kernel/postinst.d. Alternately, you can specify the command to update the boot loader by setting the 'postinst_hook' variable in /etc/kernel-img.conf. It appears that you missed the words 'specify the command'. Now, what triggers the /usr/bin/yes still remains a mistery to me. You configured it to run after kernel installation/upgrade; that's what postinst_hook means. May be this program shoud be given a different name, provided it is worth keeping it ;-). 'yes' is a common Unix utility and must not be removed. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
