On Sun, 28 Mar 2010 01:25:34 -0400 (EDT), Tong wrote: > > Long story, I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now > I can't go back, because grub-common is listed as a dependency of grub- > legacy. But the grub-common package has been upgraded for use with > version 2 only.
I don't mean to make light of your problem, but this reminds me of an old bath soap commercial. Many years ago, Dial soap had an advertising slogan that went like this: Aren't you glad you use Dial? Don't you wish everybody did? s/Dial/lilo/ No doubt my friends and acquaintances on this list will accuse me of having a lilo "fixation", but this opportunity was too good to pass up. But seriously, it's obvious that somebody messed up with the package dependencies. There's not much point in having a grub-legacy package if it can't be installed, now is there? As I see it, you have the following options: (1) Force grub-legacy to be installed with overrides to the package management system, leaving you with a "broken" package management system. (2) Live with grub-pc until somebody gets their act together and fixes this problem, or (3) Forget the whole ugly grub mess and switch to lilo. I know what I would do, but it's your call. -- .''`. Stephen Powell <zlinux...@wowway.com> : :' : `. `'` `- -- 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/1004221449.22262471269833008563.javamail.r...@md01.wow.synacor.com
