On Fri, 2011-10-14 at 12:26 -0400, Dave Jones wrote: > With todays f16 yum update, first I saw this.. > > ERROR with transaction check vs depsolve: > grub2 conflicts with (installed) grub-1:0.97-80.fc16.x86_64 > > Which I got around by doing --exclude=grub2 > When everything else had updated, I did another yum update. > This is what it did.. Looks like your mirror has grub -82, which is one of the bad builds (-81 and -82 got the phrasing of the Obsoletes: statement for grub-efi wrong). The 'working' builds (so far as we know) are grub2 1.99-9 and grub 0.97-83: if your mirror doesn't have those, wait till you do, or set up a side repo. > So now I have grub, and grub2 installed. I guess this isn't intended ? > Should I rpm -e grub ? What we 'intend' to happen is for you to wind up with both grub-efi and grub2 installed, but in fact you only need one or the other - grub2 if you boot BIOS, grub-efi if you boot EFI. > Additionally, I have a 0 byte /boot/grub2/grub.cfg, so grub2-mkconfig > isn't getting run during an update. Should it be ? That's not implemented yet. Spot filed a report requesting it, pjones says he will look at it soon: https://bugzilla.redhat.com/show_bug.cgi?id=745246 > Or is the plan for yum update'd systems to continue using grub1 ? For now this is what should happen - even with the grub *package* removed, grub will be installed in the MBR (or boot sector) until you overwrite it and grub's config will be present in /boot, so grub will continue to work. You can manually migrate to grub2 any time you choose by doing grub2-mkconfig -o /boot/grub2/grub.cfg then grub2-install /dev/foo . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
