On Tue, May 18, 2010 at 06:00:32PM -0500, Hugo Vanwoerkom <hvw59...@care2.com> 
was heard to say:
> Daniel Burrows wrote:
> >  It looks to me like something else required grub-pc, and that in
> >turn forced grub-legacy to be removed.  You could try pinning grub-pc
> >at a very low priority to see whether that helps, although without
> >knowing what's causing grub-pc to get pulled in, it's hard to say
> >whether that will really do the trick.
> >
> 
> Didn't help. I don't know what is causing grub-pc to get pulled in.

  Does adding "--show-deps -o Debug::pkgDepCache::AutoInstall=true"
to the command-line give you any more information about what's
requiring it?

  Based on what I have on my system, the obvious candidates are "grub",
"grub2", "grub-rescue-pc", and "startupmanager".

  Daniel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100519140409.gb12...@emurlahn.burrows.local

Reply via email to