Bug 18580 – Portage thinks it's upgrading (no D) from v1.0.4191-r2 to v1.0.3123-r2

• Product: Portage Development
• Status: RESOLVED INVALID

[Description klavs klavsen 2003-04-01 05:11:14 UTC]

I got this output from my emerge -u world -p:
..
[ebuild    U ] media-video/nvidia-kernel-1.0.3123-r2 [1.0.4191-r2]
[ebuild    UD] media-video/nvidia-glx-1.0.3123 [1.0.4191-r1]
..

And this is obviously wrong.

If I try emerge -Uup world it doesn't suggest the nvidia-kernel - so it seems
it's just an output typo by portage?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Actual Results:  
suggests downgrade of nvidia-kernel -but not enabling the D flag.

Expected Results:  
There should have been a D flag.

[Comment 1 Martin Holzer (RETIRED) 2003-04-01 05:55:15 UTC]

azarah: is there something with Slots ?

[Comment 2 Martin Schlemmer (RETIRED) 2003-04-01 13:15:48 UTC]

Nvidia-kernel have diff slot ... nvidia-glx do not.

[Comment 3 klavs klavsen 2003-04-01 17:18:43 UTC]

so what you're saying is that this is expected behavior - when they have different slots? if they have different slots?

[Comment 4 Martin Schlemmer (RETIRED) 2003-04-01 17:29:59 UTC]

No.  nvidia-kernel have different slots, so it only show an upgrade.  On the
other hand ... nvidia-glx have the same slot, so it is a downgrade, which is
shown correctly.

[Comment 5 klavs klavsen 2003-04-03 03:42:37 UTC]

If that's the case, then shouldn't nvidia-kernel ebuilds all have the same slots too - so it would show up correct. That way I don't accidently emerge (if I was stupid enough to automatically run emerge -Uu world f.ex.) an older version of the kernel - and not the glx (that would probably make it crash).

[Comment 6 Martin Schlemmer (RETIRED) 2003-04-03 06:39:23 UTC]

Because you might like me have two to three different kernels in use at any
one stage.

Is no bug, portage output is correct.