Bug#506008: [grub-invaders] Fails to boot

[Robert Millan]

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.

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).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."