emerge bug with slots?

Message

R.I.P. · Post by **R.I.P.** » Fri Oct 14, 2011 11:21 pm

Background:
I had 3 python versions installed 2.6,2.7,3.1, the eselected one was 2.7
Both 2.6 and 2.7 had some newer versions in portage (didn't update system for several months).
portage version is 2.1.10.27

Scenario:
I wanted to install "media-sound/solfege"
"emerge solfege" told me to rebuild python 2.7.2 with sqlite enabled in use flags
I added "dev-lang/python sqlite" in package.use (so it affected all python versions).
Then I started emerging solfege package again.
Instead of actually installing required 2.7.2 with sqlite as solfege ebuild wanted, emerge rebuilt python 2.6 and then solfege build failed because 2.7.2 was still without sqlite.
Running "emerge solfege" again solved the problem (python 2.7.2 was rebuilt), but I'm confused why it happened.

Is it a bug or some expected nontrivial emerge behavior?

krinn · Post by **krinn** » Sat Oct 15, 2011 12:03 am

python 2.6 and python 2.7 share different slots, but use the same python2 wrapper.

you must :
eselect python set --python2 python2.7
eselect python set --python3 python3versionyoulike
eselect python set pythonversionyoulike (this time it define the default python version to use when someone just call python)

R.I.P. · Post by **R.I.P.** » Sat Oct 15, 2011 1:37 am

krinn wrote:python 2.6 and python 2.7 share different slots, but use the same python2 wrapper.

you must :
eselect python set --python2 python2.7
eselect python set --python3 python3versionyoulike
eselect python set pythonversionyoulike (this time it define the default python version to use when someone just call python)

actually it was set already like this prior to all my actions - python2: 2.7, python3: 3.1, default python: 2.7
The problem is that emerge decided to rebuild wrong slot.

Actually took a look and solfege in ebuild says PYTHON_DEPEND="2:2.6"
I'm not sure how PYTHON_DEPEND is handled, but the strange thing is that 2 consequent emerges of solfege package were updating python (because of sqlite use flag added) of different versions (first 2.6, second 2.7) without any changes in between. First one failed, second one succeeded.

Jaglover · Post by **Jaglover** » Sat Oct 15, 2011 1:39 am

Even if it is a bug it probably caught nobody's attention because everybody removed 2.6 after upgrade to 2.7.

R.I.P. · Post by **R.I.P.** » Sat Oct 15, 2011 1:42 am

Jaglover wrote:Even if it is a bug it probably caught nobody's attention because everybody removed 2.6 after upgrade to 2.7.

I understand that, but that may mean that there is some bug in portage regarding slot deps.
So I'm trying to understand whether it is a bug (and if it is I'll report it to bugzilla) or some tricky intended behavior.

krinn · Post by **krinn** » Sat Oct 15, 2011 1:46 am

Jaglover wrote:Even if it is a bug it probably caught nobody's attention because everybody removed 2.6 after upgrade to 2.7.

not everybody, i'm not a depclean fan

Code: Select all

 dev-lang/python
    selected: 2.6.7-r2 3.1.4-r2 
   protected: none 
     omitted: 2.7.2-r3 3.2.2

Jaglover · Post by **Jaglover** » Sat Oct 15, 2011 1:52 am

Oh dear.
May I recommend depclean now? And maybe a beer while doing that?

krinn · Post by **krinn** » Sat Oct 15, 2011 1:54 am

Number to remove: 21

bah, i will just keep them, i still have plenty space left

Jaglover · Post by **Jaglover** » Sat Oct 15, 2011 2:05 am

Sure, I used to be a collector myself ... I was collecting stamps ... but methinks it's OK to collect just anything.