From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KU0ij-0007ay-Dd for mharc-grub-devel@gnu.org; Fri, 15 Aug 2008 10:56:05 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KU0ii-0007at-Gs for grub-devel@gnu.org; Fri, 15 Aug 2008 10:56:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KU0ih-0007ah-Bw for grub-devel@gnu.org; Fri, 15 Aug 2008 10:56:04 -0400 Received: from [199.232.76.173] (port=39416 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KU0ih-0007ae-7P for grub-devel@gnu.org; Fri, 15 Aug 2008 10:56:03 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:63312) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KU0ig-0006oL-ND for grub-devel@gnu.org; Fri, 15 Aug 2008 10:56:03 -0400 Received: from [85.180.51.117] (e180051117.adsl.alicedsl.de [85.180.51.117]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1KU0if2mu8-0000jL; Fri, 15 Aug 2008 16:56:01 +0200 From: Felix Zielcke To: The development of GRUB 2 In-Reply-To: <87myjemj4k.fsf@xs4all.nl> References: <1218732044.8610.2.camel@fz.local> <1218810370.4406.20.camel@fz.local> <87myjemj4k.fsf@xs4all.nl> Content-Type: text/plain Date: Fri, 15 Aug 2008 16:56:07 +0200 Message-Id: <1218812167.4705.11.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/57smWJqSBujjJBbLr7tsSgunHSTXB+tDJ4FE jxxOeYlV4FBkig8alm+e33tDieNMVUt3pfuZfJTL4RxBn0/peQ swbJbNW5fbUKIadALYk03dtE0aNwlAI X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) Subject: Re: [Fwd: Re: Bug#495049: grub-pc: does not boot because module "normal" is not loaded] X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2008 14:56:04 -0000 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 :((