E-mail sent to www@gentoo.org: """ Since the linux26-headers are now being uses all the Gentoo cd's are broke. You really need to update the install pages on how to use the new linux headers. This is a major issue, and you might want to fix this!!! emerge -C linux-headers $ mkdir /etc/portage && echo sys-kernel/linux26-headers ~x86 >> /etc/portage/package.keywords $ emerge --nodeps --oneshot linux26-headers Trevor Benedict """ I don't completely agree with the solution (portage/package.keywords); I actually completely disagree with it, but if linux-headers is indeed blocking linux26-headers with the result described, we need to document how to remove linux-headers and install linux26-headers. _Unless_ this only occurs when the user does something weird (such as ACCEPT_KEYWORDS="~x86") during installation. Anyone know what the deal is? Reproducible: Always Steps to Reproduce:
linux26-headers is stable on a lot of archs now, including x86 ... not sure why they felt the need to update package.keywords
So the current documentation should mention """( Installing the linux26-headers ) " " # emerge unmerge linux-headers " # emerge linux26-headers """ ?
I personally had some issues with this; after "emerge -C linux-headers" I couldn't emerge "linux26-headers" unless I used --nodeps. I hate --nodeps. I don't want to document it.
on a related note... I unmerged linux-headers because it was blocking linux26-headers. Then I emerged linux26-headers and glibc. Guess who came back as a dependency of glibc? linux-headers, no longer bothered by the existence of linux26-headers. So there's probably a bug in portage regarding blocking (it's apparently a one-way street), but I've no idea how to track it down.
A way to fix this during bootstrap is to 'echo "sys-kernel/linux-headers" >> /etc/portage/package.mask" before running bootstrap.sh. Its still a bug in 2004.3 PPC LiveCD, by the way.
Is this only for the PPC 2004.3 release media or do all media suffer from this? Does our 2004.3 (and later) documents still need to mention this? Is the package.mask trick the best way? I don't like mentioning package.mask in the installation instructions. People might get confused, want to know what it is, etc.
The blocking message seems to appear only when you rerun bootstrap (for whatever reason). Just running bootstrap installs both headers (linux26-headers is installed first, then linux-headers) without issues. This also only happens when you have "nptl" in your USE flag (of course).
I've added the following paragraph in the installation instructions: """ When you have set the nptl USE flag, rerunning bootstrap.sh might fail with a message that linux-headers blocks linux26-headers. When you receive this error, remove linux-headers and retry: Code Listing 15: Removing linux-headers from your system # emerge -C linux-headers # emerge --oneshot linux26-headers # scripts/bootstrap.sh """ jstubbs told me that this issue will get fixed in the future (not immediate though); we should verify if such actions are still needed with the 2005.0 release. On a sidenote: the reason I say "on rerun" is because I just finished running bootstrap.sh with USE="nptl" set and it finished succesfully. Both for networkless installation (with portage snapshot) and current portage. No blocking, but when I interrupted the installation and reran it it did occur.
