Bug 30047 – linux-headers is being pulled in by emerge -pUv world

• Status: RESOLVED INVALID
• Product: Portage Development

[Description Paul Thompson 2003-10-01 01:08:37 UTC]

In 'emerge -pUv world' listing:
[ebuild     U ] sys-kernel/linux-headers-2.4.19-r1 [2.4.20] 

There is no other dependancy that requires this in the upgrade list.
Plus, its not an upgrade. And its not in my world file. This shouldnt
change unless I upgrade glibc. Could this be related to bug
30041 ?

Thanks;
Paul

[Comment 1 Joshua Kinard 2003-10-01 02:02:59 UTC]

It's likely being called in because of the profile.  I'm assuming you're
running an x86 box, and the x86 profile is locked down to linux-headers-2.4.19-r1.
 Also, there is no linux-headers-2.4.20 ebuild.  This is why it's wanting
to "upgrade" (technically a downgrade).  About the only way around this is
to modify the default-x86 profile every rsync (maybe with some sed command
called from a bash script).  Eventually, things will move to linux-headers-2.4.21
and beyond.

Just edit /usr/portage/profiles/default-x86-1.4/packages, and change the
linux-headers line to reflect a greater version than 2.4.19-r1.

Gonna mark this bug as invalid as it's really not a bug in the sense of a
bug, just another example of the myriad of ways portage uses for masking
(profile-mask, keyword-mask, package.mask, think of it that way).

[Comment 2 SpanKY 2003-10-01 04:08:30 UTC]

or inject the package ... `emerge -i sys-kernel/linux-headers-2.4.19-r1`

[Comment 3 SpanKY 2003-10-01 18:56:14 UTC]

*** Bug 30102 has been marked as a duplicate of this bug. ***