Summary: | linux-headers is being pulled in by emerge -pUv world | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paul Thompson <set.mailinglist> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | kumba |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Thompson
2003-10-01 01:08:37 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). or inject the package ... `emerge -i sys-kernel/linux-headers-2.4.19-r1` |