Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 455544 - =sys-boot/grub-2.00_p5107-r1 stabilize
Summary: =sys-boot/grub-2.00_p5107-r1 stabilize
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Keywording and Stabilization (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on: 316603 485596
Blocks:
  Show dependency tree
 
Reported: 2013-02-05 02:57 UTC by Mike Gilbert
Modified: 2013-10-14 00:15 UTC (History)
8 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Gilbert gentoo-dev 2013-02-05 02:57:29 UTC
This is probably overdue.

The only blocker is the handbook update. Cardoe says he wrote a patch for that at some point.
Comment 1 juantxorena@gmail.com 2013-04-11 19:28:47 UTC
Is this going to be fixed sometime? GRUB2 is getting more and more needed since almost every computer today comes with uefi, which AFAIK needs this to work. In any case, this has been around fore months (for years if we take into account the working beta versions). I'm aware that I'm just an innocent bystander who is not going to do anything in this bug, but I'm just saying.
Comment 2 Mike Gilbert gentoo-dev 2013-04-11 19:51:36 UTC
It really isn't a high priority for me; if someone else wants to do the documentation work it will get done faster.
Comment 3 Sven Vermeulen (RETIRED) gentoo-dev 2013-08-15 06:40:16 UTC
Sorry 'bout that, got some time issues - will be working on the documentation now
Comment 4 Doug Goldstein (RETIRED) gentoo-dev 2013-08-15 19:09:33 UTC
Handbook is now updated. Let's start getting arch testers added and let's start getting this done.
Comment 5 Doug Goldstein (RETIRED) gentoo-dev 2013-08-15 19:11:11 UTC
fwiw to the amd64 ATs, I use this on a handful of amd64 machines that are stable except for running this version of grub.
Comment 6 Mike Gilbert gentoo-dev 2013-08-15 19:28:43 UTC
We have a couple of choices for the stable target:

2.00-r4: Fails to boot x86_64-efi when compiled with gcc-4.8 (bug 468136).
2.00_p5086: Fails to build the i386-mulitboot platform (bug 479764).

I can backport a patch for the latter, or just grab a new snapshot.

Thoughts?
Comment 7 Mike Gilbert gentoo-dev 2013-08-19 21:04:50 UTC
I haven't heard anything bad on 2.00_p5107; lets give it another week and use that as the target.
Comment 8 Markos Chandras (RETIRED) gentoo-dev 2013-08-20 09:54:04 UTC
(In reply to Doug Goldstein from comment #5)
> fwiw to the amd64 ATs, I use this on a handful of amd64 machines that are
> stable except for running this version of grub.

I have no objections if you want to mark this stable on amd64 yourself
Comment 9 Mike Gilbert gentoo-dev 2013-09-20 14:57:53 UTC
Please stabilize:

=sys-boot/grub-2.00_p5107-r1

Regarding Markos' comment: I would appreciate it if someone on the arch teams could give it a test. If nobody wants to, I will do it myself.
Comment 10 Pacho Ramos gentoo-dev 2013-09-21 07:21:25 UTC
Since most people have probably merged grub using "emerge grub" instead of specifying slot 0, they will probably see grub updated to 2.0 and, later, the old grub:0 being removed by depclean. Maybe this is a bit risky if people don't noticed they need to configure grub-2 properly :/ Have you think in doing a news item?
Comment 11 Mike Gilbert gentoo-dev 2013-09-21 15:01:44 UTC
I knew I was forgetting something.

Arches: Please just report your testing results, but do not commit the new keywords. I will do so after publishing a news item, as pacho suggests.
Comment 12 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2013-09-30 00:12:08 UTC
works fine for me on x86 (I submitted some documentation change recommendations to gentoo-dev)
Comment 13 Mike Gilbert gentoo-dev 2013-10-14 00:15:23 UTC
+  14 Oct 2013; Mike Gilbert <floppym@gentoo.org> grub-2.00_p5107-r1.ebuild:
+  Stable on amd64 and x86, bug 455544.
+