Bug#342542: kernel-package: linux-image postinst fails on lilo system using sarge
severity #342542 normal tags #342542 - unreproducible moreinfo thanks On Thu, Dec 08, 2005 at 11:06:47PM -0600, Manoj Srivastava wrote: If the postinst says exit 0; and the shell thinks the return value was non 0, you should file a bug against the shell you are using. This is not a kernel-package bug. Actually, I don't agree any more. From an strace, it looks like the hook script's output (update-grub in my case) gets piped to debconf, which doesn't understand the output and issues errors: read(8, VERSION 2.0\n, 4096) = 12 write(7, 0 2.0\n, 6) = 6 read(8, CAPB backup\n, 4096) = 12 write(7, 0 multiselect backup\n, 21) = 21 read(8, Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB men..., 4096) = 47 read(8, found: /boot/grub/menu.lst .\n, 4096) = 29 write(7, 20 Unsupported command \testing\..., 153) = 153 read(8, Searching for splash image... , 4096) = 30 read(8, none found, skipping...\n, 4096) = 24 write(7, 20 Unsupported command \searchin..., 133) = 133 read(8, Found kernel: /boot/vmlinuz-2.6, 4096) = 43 write(7, 20 Unsupported command \found\ (..., 118) = 118 read(8, Found kernel: /boot/vmlinuz-2.6, 4096) = 43 write(7, 20 Unsupported command \found\ (..., 118) = 118 read(8, Found kernel: /boot/vmlinuz-2.6, 4096) = 41 write(7, 20 Unsupported command \found\ (..., 116) = 116 read(8, Updating /boot/grub/menu.lst .., 4096) = 33 read(8, done\n, 4096) = 5 write(7, 20 Unsupported command \updating..., 116) = 116 read(8, \n, 4096) = 1 write(7, 20 Unsupported command \\ (full ..., 71) = 71 read(8, , 4096) = 0 This might be the reason why most debug output isn't printed as well. Oh yeah, and I think that STFERR in linux-image.postinst line 1102 should be STDERR. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342542: kernel-package: linux-image postinst fails on lilo system using sarge
Package: kernel-package
Version: 10.011
Severity: minor
Installing a linux-image built on sid with kernel-package 10.011 fails
on a sarge system using lilo. It looks like the postinst script
doesn't properly handle lilo's zero return code. I have added debug
output to the postinst:
if (-T /etc/$loader.conf) {
# Trust and use the existing lilo.conf.
print You already have a $Loader configuration in /etc/$loader.conf\n;
warn use lilo.conf\n;
my $ret = run_lilo();
warn ret $ret\n;
exit $ret;
warn after exit\n;
}
and here is the output of that script
$ DEBUG=yes sudo /var/lib/dpkg/info/linux-image-2.6.14.3-zgsrv.postinst
configure
vmlinuz(/boot/vmlinuz-2.6.14.3-zgsrv) points to /boot/vmlinuz-2.6.14.3-zgsrv
(/boot/vmlinuz-2.6.14.3-zgsrv) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.14.3-zgsrv.postinst line 580, STDIN line 2.
use lilo.conf
ret 0
$ echo $?
128
$ less
This, of course, makes aptitude barf.
What I find strange is, that an explicit exit 0 right after the
run_lilo call makes the shell say 128, and an explicit exit 0
right before the run_lilo makes the shell say 0 as it should be.
This is very strange. Any ideas?
I inspected the changelog of current kernel_package and didn't find
any entries that indicate that this issue was fixed in more recent
versions of kernel-package.
Greetings
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342542: kernel-package: linux-image postinst fails on lilo system using sarge
Hi, If the postinst says exit 0; and the shell thinks the return value was non 0, you should file a bug against the shell you are using. This is not a kernel-package bug. manoj -- Love conquers all things; let us too surrender to love. Publius Vergilius Maro (Virgil) Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342542: kernel-package: linux-image postinst fails on lilo system using sarge
tags #342542 unreproducible moreinfo thanks On Thu, Dec 08, 2005 at 11:06:47PM -0600, Manoj Srivastava wrote: If the postinst says exit 0; and the shell thinks the return value was non 0, you should file a bug against the shell you are using. This is not a kernel-package bug. I agree. However, my shell is bash, and it might be as well a perl issue, but if it happens with kernel-images built by kernel-package, and it might happen on other systems as well, this bug should remain visible to avoid it from being filed again. Additionally, if it can be worked around in kernel-package, it is most probably the easiest way to work around there. For the record: I am using bash. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
