Your message dated Wed, 26 Aug 2009 19:19:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#543615: dependency between grub2 and grub-pc
preventing each from installing
has caused the Debian Bug report #543615,
regarding subprocess installed post-installation script returned error exit
status 10
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.)
--
543615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543615
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-pc
Version: 1.96+20090825-1
Severity: important
File: grub
dpkg --pending --configure
Setting up grub-pc (1.96+20090825-1) ...
dpkg: error processing grub-pc (--configure):
subprocess post-installation script returned error exit status 10
Errors were encountered while processing:
grub-pc
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/disk/by-uuid/ae7d5095-c8b3-4205-af0e-032b0e124ec3 / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda5 /heretix reiserfs rw,nodev,noexec,relatime 0 0
/dev/sda8 /home ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda3 /scratch ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda9 /opt/ddr ext3 rw,relatime,errors=continue,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
*********************** END /boot/grub/device.map
*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinux-2.6.30-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinux-2.6.30-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.30-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.30-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.30-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.29-1-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.29-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.29-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.29-1-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.29-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.29-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.28.3" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.28.3
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.28.3
}
menuentry "Debian GNU/Linux, Linux 2.6.28.3 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.28.3
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.28.3
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.26-2-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-2-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.26-2-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.26-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-1-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.26-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.26-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.26-1-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.26-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.26-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.25-2-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.25-2-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.25-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.25-2-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.25-2-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.25-2-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.24-1-amd64" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.24-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro
initrd /boot/initrd.img-2.6.24-1-amd64
}
menuentry "Debian GNU/Linux, Linux 2.6.24-1-amd64 (recovery mode)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
linux /boot/vmlinuz-2.6.24-1-amd64
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro single
initrd /boot/initrd.img-2.6.24-1-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86 ###
menuentry "Memory test (memtest86)" {
linux /memtest86.bin
}
### END /etc/grub.d/20_memtest86 ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux /memtest86+.bin
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/22_invaders ###
menuentry "GRUB Invaders" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set ae7d5095-c8b3-4205-af0e-032b0e124ec3
multiboot /boot/invaders
}
### END /etc/grub.d/22_invaders ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*********************** END /boot/grub/grub.cfg
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (900, 'stable'), (500, 'testing'), (300, 'unstable'), (290,
'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (1,
'experimental-i386'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii grub-common 1.96+20090825-1 GRand Unified Bootloader, version
ii libc6 2.9-23 GNU C Library: Shared libraries
ii ucf 3.0016 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
pn desktop-base <none> (no description available)
ii genisoimage 9:1.1.9-1 Creates ISO-9660 CD-ROM filesystem
-- debconf information:
* grub-pc/linux_cmdline:
grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: false
grub-pc/kopt_extracted: false
grub-pc/postrm_purge_boot_grub: false
grub2/linux_cmdline_default: quiet
grub-pc/install_devices:
--- End Message ---
--- Begin Message ---
Version: 1.96+20090826-2
Am Mittwoch, den 26.08.2009, 16:25 +0200 schrieb Felix Zielcke:
> Am Mittwoch, den 26.08.2009, 17:09 +0300 schrieb Hristo Hristov:
> > Package: grub-pc
> > Version: 1.96+20090826-1
> > Severity: normal
> >
> > This bug seem to be still present in version 1.96+20090826-1:
>
> Unfortunately yes, but luckly I just uploaded -2 before the dinstall run
> so you're probable the only one who noticed this :)
>
Is now on the mirrors. Though it has still another problem if you have
multiple kernel parameters.
--
Felix Zielcke
Proud Debian Maintainer
--- End Message ---
