Your message dated Thu, 20 Nov 2008 15:51:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: [grub-invaders] Fails to boot
has caused the Debian Bug report #506008,
regarding [grub-invaders] Fails to boot
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.)


-- 
506008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506008
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub-invaders
Version: 1.0.0-8
Severity: grave
Tags: patch

--- Please enter the report below this line. ---
Hi,

While trying grub-pc, I went over grub-invaders. Installation went fine, but it 
failed to boot with an error like "multiboot unknown" (can't remember exactly).

The attached patch solves the issue (at least for me).

It moves line 10 ( prepare_grub_to_access_device…) after line 6, so that the 
menuentry contains only the multiboot, which is then recognised (for an unknown 
reason).

Regards, 

OdyX

--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.27-1-amd64

Debian Release: lenny/sid
  700 testing         mirror.switch.ch 
  600 unstable        pkg-fso.alioth.debian.org 
  600 unstable        mirror.switch.ch 
  500 testing-proposed-updates mirror.switch.ch 
   50 unstable        mirror.switch.ch 
   50 unstable        ftp.uni-kl.de 
   50 testing-proposed-updates mirror.switch.ch 
   50 testing         mirror.switch.ch 
   50 testing         ftp.uni-kl.de 
   50 kernel-dists-trunk kernel-archive.buildserver.net 
   50 kernel-dists-sid kernel-archive.buildserver.net 
   50 experimental    mirror.switch.ch 
   50 experimental    ftp.uni-kl.de 

--- Package information. ---
Depends       (Version) | Installed
=======================-+-===========
                        | 



-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]
--- etc/grub.d/22_invaders	2008-08-04 11:07:08.000000000 +0200
+++ /etc/grub.d/22_invaders	2008-11-17 17:16:01.000000000 +0100
@@ -4,11 +4,10 @@
   source /usr/lib/grub/update-grub_lib
   INVADERSPATH=$( make_system_path_relative_to_its_root "/boot/invaders" )
   echo "Found GRUB Invaders image: /boot/invaders" >&2
-  cat << EOF
-menuentry "GRUB Invaders" {
-EOF
+
   prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/g"
   cat << EOF
+menuentry "GRUB Invaders" {
 	multiboot	${INVADERSPATH}
 }
 EOF

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
Le mercredi 19 novembre 2008 19:20:20 Robert Millan, vous avez écrit :
> On Wed, Nov 19, 2008 at 05:03:10PM +0100, Didier Raboud wrote:
> > OK.
> >
> > I begin to understand... ( #497791 )
> >
> > The problem is that if you only run "update-grub", "grub-install
> > <device>" is not run automagically and will then put grub in a weird
> > state.
> >
> > "grub-install <device>" should be run after each update-grub if I
> > understand correctly - right ?
>
> grub-install should be run often, but only by the user.  It's too risky to
> run automatically.

OK. I think that this is not clear though : nothing in /usr/share/doc/grub-pc 
nor anywhere where I could find it. Maybe there is something to do…

> So, to summarize, if you grub-install with the versions of grub-pc /
> grub-common in sid, invaders works, but if you grub-install with the ones
> in experimental, it doesn't?  (disregard update-grub calls in this test,
> but make sure you're using /etc/grub.d/*_multiboot unmodified).

Lenny/Sid version :     everything boots and works
Experimental version :  everything boots, but no background image

        The experimental version wants to use the old desktop-base image 
(another bug…)

So, the issue was simply to run 'grub-install <device>' after each grub-update 
to be sure that everything is copied correctly in /boot.

I'm closing the bug with '-done', because it was my mis-use of the package.

Regards, 

OdyX

-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to