Re: pinning + apt-get vs aptitude
- To: email@example.com
- Subject: Re: pinning + apt-get vs aptitude
- From: Daniel Burrows <firstname.lastname@example.org>
- Date: Wed, 19 May 2010 07:04:09 -0700
- Message-id: <20100519140409.GB12104@emurlahn.burrows.local>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <20100516144424.GA22637@emurlahn.burrows.local> <email@example.com>
On Tue, May 18, 2010 at 06:00:32PM -0500, Hugo Vanwoerkom <firstname.lastname@example.org> 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
Based on what I have on my system, the obvious candidates are "grub",
"grub2", "grub-rescue-pc", and "startupmanager".