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 :(( _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
