Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 398451 - sys-boot/grub-static blocker on sys-boot/grub should be sys-boot/grub:0
Summary: sys-boot/grub-static blocker on sys-boot/grub should be sys-boot/grub:0
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: AMD64 Project
Depends on:
Reported: 2012-01-11 00:34 UTC by Duncan
Modified: 2012-07-23 03:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Duncan 2012-01-11 00:34:44 UTC
I'm /investigating/ upgrading to grub2.  As such, I've not actually installed it yet as I'm still resolving problems with doing so like this one, so can't /confirm/ the lack of file collisions, but from all I've read so far, grub2, aka grub:2 aka >=grub-1.99 renames all possibly colliding files to grub2 versions, and is slotted :2 precisely to allow installation beside grub-legacy, so there /should/ be no collisions.

Further, grub:0 and grub:2 don't appear to block each other, and grub-static corresponds to grub:0, so while it should indeed block grub:0, I don't see how a full block on all grub slots, the current blocker, can be valid.  The closest grub:0/grub:2 colliding bug I saw tho was back with grub-1.98, and the resolution and comments appear to indicate that there should now be no conflicts, thus this bug.

(That said, if there's some valid reason for the all-slots block, feel free to close this bug.  I did look but didn't see anything since the already mentioned 1.98 bug, which appeared to indicate that the collisions should be resolved now, so...)
Comment 1 Duncan 2012-01-17 07:18:42 UTC
OK, all upgraded to grub:2 now, and I can confirm that there's no file collisions between it and grub-static.

FWIW I have four disks partitioned identically, with most of the system in a number of 4-way md/raid-1s.  However, I have /boot as two separate two-disk raid-1s, so I can upgrade kernels and in this case grub on the one two-disk set, while leaving the other safely alone until after I've test-booted from both of the disks in the one two-disk raid-1 by itself.  Once that's working to my satisfaction, I can upgrade the other one.

That's why I wanted to keep grub-static around over the upgrade, since I was only playing around with the one md/raid /boot array, while grub-static remained on the other one.  The only problem with the idea was the too-broad blocker grub-static has on all of grub, when it should only be against sys-boot/grub:0, aka <=sys-boot/grub-1.90, or some such (current grub:2 being 1.99-r2, with the changelog listing versions back to 1.91 in 2005, so <=1.90 should do quite nicely, or make it <1.99 if desired, since the file collisions were resolved with 1.98).

grub-static's no longer on my system and I must say it's nice to be be able to build everything on my no-multilib system once again, but the security of having grub-static still installed and workable on the two drives, should the grub2 I was learning on the other two wasn't yet setup properly, was very nice to have! =:^)
Comment 2 Tomáš Chvátal (RETIRED) gentoo-dev 2012-02-27 16:36:24 UTC
The blocker indeed should be updated. PRoblem is that the ebuild also needs to be migrated to newer eapi.