Your message dated Tue, 13 Jul 2010 02:42:01 +0100
with message-id <[email protected]>
and subject line Re: Bug#586677: grub-common: fails to update menu.lst with 
grub-legacy; new version in unstable fixes it
has caused the Debian Bug report #586677,
regarding grub-common: fails to update menu.lst with grub-legacy; new version 
in unstable fixes it
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.)


-- 
586677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586677
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-common
Version: 1.98+20100617-1
Severity: important
Tags: squeeze

Hi,

the current version of grub-common in testing (1.98-1) breaks update-grub when
using grub-legacy.
It does nothing, all it says is:

/boot/grub# update-grub
Searching for GRUB installation directory ... found: /boot/grub
/boot/grub#


Updating to the version in unstable (1.98-20100617-1) solves this problem.

Regards,
Pedro



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 
'testing-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.34-toi-a4dj (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grub-common depends on:
ii  base-files              5.7              Debian base system miscellaneous f
ii  dpkg                    1.15.7.2         Debian package management system
ii  gettext-base            0.17-11          GNU Internationalization utilities
ii  install-info            4.13a.dfsg.1-5   Manage installed documentation in 
ii  libc6                   2.11.1-3         Embedded GNU C Library: Shared lib
ii  libdevmapper1.02.1      2:1.02.48-1      The Linux Kernel Device Mapper use
ii  libfreetype6            2.3.11-1         FreeType 2 font engine, shared lib
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages grub-common recommends:
ii  os-prober                     1.35       utility to detect other OSes on a 

Versions of packages grub-common suggests:
pn  grub-emu                      <none>     (no description available)
pn  multiboot-doc                 <none>     (no description available)
pn  xorriso                       <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.98+20100527-1

On Mon, Jun 21, 2010 at 05:26:43PM +0100, Pedro Ribeiro wrote:
> On 21 June 2010 17:18, Colin Watson <[email protected]> wrote:
> > On Mon, Jun 21, 2010 at 04:53:51PM +0100, Pedro R wrote:
> >> the current version of grub-common in testing (1.98-1) breaks update-grub 
> >> when
> >> using grub-legacy.
> >> It does nothing, all it says is:
> >>
> >> /boot/grub# update-grub
> >> Searching for GRUB installation directory ... found: /boot/grub
> >> /boot/grub#
> >>
> >>
> >> Updating to the version in unstable (1.98-20100617-1) solves this problem.
> >
> > Your Version: above doesn't seem to make sense in light of this comment.
> > The Version: field should be the version in which you found the bug, not
> > a version that seems to fix it.
> >
> > I'm not sure what might have fixed this, anyway.  Could you please run:
> >
> >  which update-grub
> >  bash -x /usr/sbin/update-grub
> >
> > ... and show me the output?
> 
> Sorry, I sent this bug report after upgrading to the unstable version.
> 
> I'm sending the output of the unstable version (update-grub-good) and
> the output of the testing version (update-grub-bad).

OK, that indicates that this was very probably #550704.  I'm closing
this bug with this message; with a little bit more luck, a fixed version
should reach testing this weekend.

Thanks,

-- 
Colin Watson                                       [[email protected]]


--- End Message ---

Reply via email to