Bug#707653: marked as done (grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr))

[Debian Bug Tracking System]

Your message dated Sun, 11 Aug 2013 12:25:11 +0100
with message-id <20130811112511.GK27110 at riva.ucam.org>
and subject line Re: Bug#707653: grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)
has caused the Debian Bug report #707653,
regarding grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)
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 owner at bugs.debian.org
immediately.)


-- 
707653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707653
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Musenbrock <redeamer at gmx.net>
Subject: grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)
Date: Fri, 10 May 2013 00:46:19 +0200
Size: 3886
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20130811/b083935c/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Colin Watson <cjwatson at debian.org>
Subject: Re: Bug#707653: grub2-common: After Grub 2.00-14 upgrade, system failed to boot (rescue, old grub 1.99 still in mbr)
Date: Sun, 11 Aug 2013 12:25:11 +0100
Size: 4624
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20130811/b083935c/attachment-0001.mht>