emerge 'loop'

[keanu]

Is this a problem with the ebuilds of cdrtools or something i did wrong?
When i update world it wants to install 1.11.33 if i have 2.01_alpha05 installed, and when i have 2.01_alpha05 installed it wants to install 1.11.33

First i thought it was a slot problem, but there all in slot 0

Code: Select all

 
# emerge -puv world --deep

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild    UD] app-cdr/cdrtools-1.11.33 [2.01_alpha05]

trinity root # emerge -ku world --deep
Calculating world dependencies ...done!
>>> emerge (1 of 1) app-cdr/cdrtools-1.11.33 to /
<cut>
 app-cdr/cdrtools
    selected: 2.01_alpha05
   protected: 1.11.33
     omitted: none
<cut>
# emerge -puv world --deep

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild    U ] app-cdr/cdrtools-2.01_alpha05 [1.11.33]

trinity root # emerge -ku world --deep
Calculating world dependencies ...done!
>>> emerge (1 of 1) app-cdr/cdrtools-2.01_alpha05 to /
<cut>
 app-cdr/cdrtools
    selected: 1.11.33
   protected: 2.01_alpha05
     omitted: none
<cut>
# emerge -puv world --deep

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild    UD] app-cdr/cdrtools-1.11.33 [2.01_alpha05]

[Jimbow]

I've got the same problem. I've got other packages from emerge -up world that I don't want to emerge right now (like downgrading the latest Nvidia drivers). So I do

Code: Select all

emerge -up world
emerge X Y Z

where X Y Z are specific packages listed from the emerge -up world. This is pretty painless. But nonetheless it would be nice if the cdrtools loop was closed.

[vikwiz]

I can confirm this 'flipping' of versions, too.
No solution yet, except using -k, so no rebuild neccessary.

[keanu]

its on bugs and for a long time it seems, i guess someone will get around to fixing it when they have time

http://bugs.gentoo.org/show_bug.cgi?id=13574