Summary: | Emerge mistaken a Downgrade with an Upgrade | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Isam Bayazidi <isam> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Isam Bayazidi
2003-09-07 18:15:49 UTC
Did you change kernels after emerging nvidia-kernel ? If yes it is a SLOT change and the kernel modules would be installed for the new kernel and it's not a downgrade for portage. No, I did not change the kernel, infact, this update appeared a minute after I emerged media-video/nvidia-kernel-1.0.4496 .. so it is related to the fact that nvidia-kernel-1.0.4496 is "~x86" while my default system setting is "x86". and I only have one nvidia-kernel installed, so it is not a slot. I get this too. emerge -up world yields: . . . [ebuild U ] gnome-extra/gnome-vfs-extras-0.99.10 [0.99.11] . . . This is caused by slots. |