Your message dated Tue, 9 Nov 2010 19:13:56 +0000 with message-id <[email protected]> and subject line Re: Bug#602940: linux-image-2.6.32-5-686_2.6.32-27_i386.deb has caused the Debian Bug report #602940, regarding linux-image-2.6.32-5-686_2.6.32-27_i386.deb to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 602940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602940 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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/2 S+ 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 <-- !!!
--- End Message ---
--- Begin Message ---On Tue, Nov 09, 2010 at 05:31:33PM +0100, Ennio-Sr wrote: > > 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 [...] > Running yes. > User postinst hook script [yes] failed to execute: No such file or directory > ^^^^^^^^^^^^^^^^^ [...] This is your configuration error. Remove the line 'postinst_hook = yes' from /etc/kernel-img.conf. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus
--- End Message ---
