Your message dated Thu, 27 Aug 2009 08:09:30 +0200
with message-id <[email protected]>
and subject line Re: Bug#543789: grub-pc: failed to upgrade
has caused the Debian Bug report #543789,
regarding grub-pc: failed to upgrade
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.)
--
543789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543789
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-pc
Version: 1.96+20090826-1
Severity: grave
Justification: renders package unusable
Hi,
when I upgraded my system this morning, grub-pc failed to upgrade
(from 1.96+20090808-1 to 1.96+20090826-1) in configure stage.
Downgrading to 1.96+20090808-1 fixed the problem. So my system has
1.96+20090808-1 at present (i.e. I'm writing this email with grub-pc
of 1.96+20090808-1), sorry if that caused any inconvenience for you.
Thanks for your maintenance. Regards.
-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/disk/by-uuid/946fa743-3466-4430-8adb-2ed4313a1945 / ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/hda5 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/hdd1 /seci ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/hdd2 /secii ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/hdd3 /seciii ext3 rw,relatime,errors=continue,data=ordered 0 0
*********************** END /proc/mounts
*********************** BEGIN /boot/grub/device.map
(hd0) /dev/hda
(hd1) /dev/hdd
*********************** 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
set timeout=5
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
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
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.30-1-686" {
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
linux /boot/vmlinuz-2.6.30-1-686
root=UUID=946fa743-3466-4430-8adb-2ed4313a1945 ro vga=791
initrd /boot/initrd.img-2.6.30-1-686
}
menuentry "Debian GNU/Linux, Linux 2.6.30-1-686 (recovery mode)" {
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
linux /boot/vmlinuz-2.6.30-1-686
root=UUID=946fa743-3466-4430-8adb-2ed4313a1945 ro single
initrd /boot/initrd.img-2.6.30-1-686
}
menuentry "Debian GNU/Linux, Linux 2.6.29-2-686" {
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
linux /boot/vmlinuz-2.6.29-2-686
root=UUID=946fa743-3466-4430-8adb-2ed4313a1945 ro vga=791
initrd /boot/initrd.img-2.6.29-2-686
}
menuentry "Debian GNU/Linux, Linux 2.6.29-2-686 (recovery mode)" {
set root=(hd0,2)
search --no-floppy --fs-uuid --set 946fa743-3466-4430-8adb-2ed4313a1945
linux /boot/vmlinuz-2.6.29-2-686
root=UUID=946fa743-3466-4430-8adb-2ed4313a1945 ro single
initrd /boot/initrd.img-2.6.29-2-686
}
### END /etc/grub.d/10_linux ###
### 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: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.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.27 Debian configuration management sy
ii grub-common 1.96+20090808-1 GRand Unified Bootloader, version
ii libc6 2.9-25 GNU C Library: Shared libraries
ii ucf 3.0020 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
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: true
grub-pc/kopt_extracted: false
grub-pc/postrm_purge_boot_grub: false
grub2/linux_cmdline_default: quiet
* grub-pc/install_devices: /dev/hda
--- End Message ---
--- Begin Message ---
Version: 1.96+20090826-3
Am Donnerstag, den 27.08.2009, 08:40 +0900 schrieb Atsuhito KOHDA:
> Package: grub-pc
> Version: 1.96+20090826-1
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> when I upgraded my system this morning, grub-pc failed to upgrade
> (from 1.96+20090808-1 to 1.96+20090826-1) in configure stage.
>
> Downgrading to 1.96+20090808-1 fixed the problem. So my system has
> 1.96+20090808-1 at present (i.e. I'm writing this email with grub-pc
> of 1.96+20090808-1), sorry if that caused any inconvenience for you.
>
> Thanks for your maintenance. Regards.
>
This has been fixed in -2 though there was another bug which was fixed
in -3 so using that version to close the bug.
I wonder how you got -1
-1 and -2 were installed during the same dinstall run so -1 shouldn't be
ever included in the Packages file.
--
Felix Zielcke
Proud Debian Maintainer
--- End Message ---
