On Tue, 2012-03-20 at 19:24 -0600, Chris Murphy wrote: > After a yum update a few minutes ago, GRUB's kinda messed up. Anyone > else? > > Right off the bat I get these two (2nd is a continuation of the 1st): > > http://dl.dropbox.com/u/3253801/first.png > http://dl.dropbox.com/u/3253801/second.png > > > Which apparently fails, because I then get this: > > http://dl.dropbox.com/u/3253801/third.png > > Which, is not right, it's missing the primary/default "Fedora Linux" > option which should boot the newly updated and current kernel. If I > choose this Advanced option, or let it time out, I get this: > > http://dl.dropbox.com/u/3253801/fourth.png > > > > Eventually it boots, but uname -r indicates 3.3.0-0.rc7.git0.3 not > 3.3.0-1. > > So is this a problem with grubby? I'm guessing it's the new grub2. I think I've seen another report of problems installing new kernels after the grub2 update, but I don't see any bug filed. Can someone file a bug on this, please? > Or is this ... wait. Why does the GRUB2 menu says it's GRUB version > 2.00~beta2, and yet yum says what's installed is 1.99-19 from repo > koji-override-1? pjones wasn't aware of the Fedora naming conventions for pre-release packages, so he just called 2.00~beta2 '1.99-19'. Properly, it ought to be versioned grub2-2.00-0.1.beta2.fc17. (Or possibly grub2-2.00-0.1.~beta2.fc17, I really dunno what that tilde is for). We will likely fix this up in a future build. The code is indeed 2.00~beta2, so '1.99-19' is a substantial jump from 1.99-18. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
