All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Fwd: Re: Bug#495049: grub-pc: does not boot because module "normal" is not loaded]
Date: Fri, 15 Aug 2008 16:56:07 +0200	[thread overview]
Message-ID: <1218812167.4705.11.camel@fz.local> (raw)
In-Reply-To: <87myjemj4k.fsf@xs4all.nl>

Hello Marco,

Am Freitag, den 15.08.2008, 16:46 +0200 schrieb Marco Gerards:

> Perhaps he simply clicked on "newest version" without bothering to
> make sure?  I can image such things just happen...

Right your not a Debian guy ;)

-- Package-specific info:
[...]

Because of this I can be sure that he used the `reportbug' or maybe the
`reportbug-ng' program/script 
I don't know anything about the -ng version except that's it's graphical
instead of console.

At least for `reportbug' I can say that it luckly get's the version
number from `dpkg'.
You don't need to find the version out yourself, or even have to choose
from a list.
But the whole things `reportbug' sends to the Debian BTS is shown in
your favourite editor where you have to add your actual bug report
before it get's send to bugs.debian.org
I hope he's just not that intelligent to choose the right severity or
make a correct bug report.
Hopefully he wasn't that smart to change the version number `reportbug'
put in the report.

Maybe he installed an earlier version and used grub-install only on that
i.e. real GRUB is outdated, but the report was made after the grub-pc
package was updated to that version.

I really hope that it's just his fault instead of that GRUB still has a
bug which can lead to this fd0 problem :((




  reply	other threads:[~2008-08-15 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 16:40 [Fwd: Re: Bug#495049: grub-pc: does not boot because module "normal" is not loaded] Felix Zielcke
2008-08-15 14:26 ` Felix Zielcke
2008-08-15 14:46   ` Marco Gerards
2008-08-15 14:56     ` Felix Zielcke [this message]
2008-08-15 15:00       ` Bean
2008-08-16 12:24         ` Robert Millan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1218812167.4705.11.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.