Python yo-yo [Solved]

[ReemZ]

On my 32-bit machine, after of course performing an equo update, I upgraded equo itself by equo install equo --ask --verbose, which installed dev-lang/python-2.7.1-r1 as a new package. I then ran equo update again just to be sure, then equo upgrade --ask --verbose...which removed dev-lang/python-2.7.1-r1 again!
Last night when I performed the same actions on my laptop (the 64-bit troublemaker), I did not see this behaviour.

So now, on my 32-bit machine, I still have python-2.6.6-r1 installed, 2.7.1-r1 is not installed.
When trying to reinstall it, is get the following:

Code: Select all

Sm0kerZ-ParadiZe ~ # equo install dev-lang/python --ask --verbose
>>  @@ These are the chosen packages:
>>    # (1/1) [sabayonlinux.org] dev-lang/python-2.7.1-r1
>>     Versions: Not installed / NoTag / NoRev ===> 2.7.1-r1 / NoTag / 0
>>      Action:          Install
>>  @@ Packages involved: 1
     Would you like to continue with dependencies calculation ? [Yes/No]
>>  @@ Calculating dependencies ...
>>  @@ These are the packages that would be installed:
>>  ## [N] [sabayonlinux.org] dev-lang/python-2.7.1-r1|0
>>  @@ These are the packages that would be removed (conflicting/substituted):
>>    ## [W] [from: sabayonlinux.org] app-portage/gentoolkit-0.3.0_rc10-r1
>>  @@ Packages needing to be installed/updated/downgraded: 1
>>  @@ Packages needing to be removed: 1
>>  @@ Packages needing to be installed: 1
>>  @@ Packages needing to be reinstalled: 0
>>  @@ Packages needing to be updated: 0
>>  @@ Packages needing to be downgraded: 0
>>  @@ Download size: 0b
>>  @@ Used disk space: 29.6MB
>>  @@ You need at least: 42.7MB of free space
     Would you like to execute the queue ? [Yes/No]

It now wants to remove gentoolkit-0.3.0_rc10-r1, which was just installed in the equo upgrade sequence. Cancelled it.
On my 64-bit machine I have both versions installed.

Did I mess up something?

[dunsurfin]

I don't know if this is any help but on my 32bit machine I have both those versions of python installed and that version of gentoolkit.
I would be tempted to do

Code: Select all

equo update --force

and then

Code: Select all

equo upgrade --ask

.

[ReemZ]

I don't know if this is any help but on my 32bit machine I have both those versions of python installed and that version of gentoolkit.
I would be tempted to do

Code: Select all

equo update --force

and then

Code: Select all

equo upgrade --ask

.

Code: Select all

>>  @@ These are the packages that would be installed:
>>  ## [N] [sabayonlinux.org] dev-lang/python-2.7.1-r1|0
>>  ## [U] [sabayonlinux.org] sys-apps/entropy-1.0_beta5|0   [1.0_beta4|0]
>>  ## [U] [sabayonlinux.org] app-admin/equo-1.0_beta5|0   [1.0_beta4|0]
>>  ## [U] [sabayonlinux.org] app-admin/sulfur-1.0_beta5|0   [1.0_beta4|0]
>>  ## [U] [sabayonlinux.org] sys-apps/entropy-client-services-1.0_beta5|0   [1.0_beta4|0]
>>  @@ These are the packages that would be removed (conflicting/substituted):
>>    ## [W] [from: sabayonlinux.org] app-portage/gentoolkit-0.3.0_rc10-r1
>>  @@ Packages needing to be installed/updated/downgraded: 5
>>  @@ Packages needing to be removed: 1
>>  @@ Packages needing to be installed: 1
>>  @@ Packages needing to be reinstalled: 0
>>  @@ Packages needing to be updated: 4
>>  @@ Packages needing to be downgraded: 0
>>  @@ Download size: 701.4kB
>>  @@ Used disk space: 29.6MB
>>  @@ You need at least: 45.1MB of free space

Ran it, last four lines:

Code: Select all

>>  @@ Installation complete.
>>  @@ Nothing to remove.
>>  @@ There are more updates to install, reloading Entropy.
>> Another Entropy is currently running.

Forced again, nothing exciting this time.
I now have both versions of python installed, as well as gentoolkit...even if equo told me it was going to remove it
Entropy works in mysterious way...

[genfool]

not sure here but, what version of entropy do you have, latest here is 1.0_beta5

equo update, equo install equo entropy

[ReemZ]

not sure here but, what version of entropy do you have, latest here is 1.0_beta5

equo update, equo install equo entropy

See above
With today's update, Entropy was updated from beta4 to beta5 (I update on a daily basis)

[albfneto]

to avoid this python yo-yo, you need to install python 2.7. then see if python 2.6 is the active python version.

Code: Select all

eselect python list

YOU MAY SEE:
^[[Aalbfneto@sabayon ~ $ eselect python list
Available Python interpreters:
  [1]   python2.6 *
  [2]   python2.7


If you see this, run the command:

Code: Select all

sudo eselect python set 2  (2 is the number of Python 2.7


if necessary, repeat "equo update && equo upgrade" commands. avoid run python-updater.

[ReemZ]

to avoid this python yo-yo, you need to install python 2.7. then see if python 2.6 is the active python version.

Code: Select all

eselect python list

YOU MAY SEE:
^[[Aalbfneto@sabayon ~ $ eselect python list
Available Python interpreters:
  [1]   python2.6 *
  [2]   python2.7


If you see this, run the command:

Code: Select all

sudo eselect python set 2  (2 is the number of Python 2.7


if necessary, repeat "equo update && equo upgrade" commands. avoid run python-updater.

Obrigado Alberto, I'll try this
Is python-updater Portage-specific?

[ReemZ]

Checked, on both systems it showed 2.7 as selected

[albfneto]

yes, python-updater is a command for Portage.
If you repeat the commands "equo update" and "equo upgrade", mantaining the python 2.7 active, the problem continue?
If yes, run as root:

Code: Select all

equo libtest && equo deptest


another thing: you uses both Portage and ALSO Entropy, in the same installation of Sabayon?
If this, edit the file /etc/entropy/client.conf, and changes "disable" to "enable", in the session "ignore-pseudo-downgrades", and not use Portage to install python, since may be different versions.

[ReemZ]

That's the funny thing, equo told me it was going to remove gentoolkit, but after running the upgrade sequence it turned out gentoolkit was still there. What puzzled me even more though was one upgrade sequence installing python 2.7 ánd removing it again. After installing python 2.7 it stayed put though and no other problems or mysteries have arisen since. Perhaps I performed the upgrade just as Joost was playing with the repos
I'll run the dep- and libtests and report back here when done, but tbh I don't expect to find anything out of the ordinary.

As for mixing package managers, I hardly ever touch Portage, and on the rare occasion that I do, I make sure to let Entropy know about it