how to upgrade to 4.1 from 4

[WarraWarra]

sry

Code: Select all

python-updater

spelling mistake.

Something else python related is causing the problem.

Maybe use:
tar xvfjp /var/lib/entropy/packages/x86/4/app-admin:equo-0.95.8~0.tbz2 -C /
Where tar extracts equo then -C to root partition to replace broken files equo files ?
Can do the same with python if you have the file for python.
/var/lib/entropy/packages/x86/4/dev-lang:python-2.5.4-r2~1.tbz2
You can http download "save to desktop" from the mirrors and try this.

Is emerge also giving problems python related ?

[albfneto]

yes do.
when i try:

Code: Select all

emerge anything or
emerge -s anything
or
python -updater
or
portato
or sulfur
or
 equo anything


the output of command..... BUS errors! in Portuguese, erros de barramento!
and the comp extremely slow, as without RAM, bu only in this Sabayon installation!
neither works!

[WarraWarra]

I will download 4.0-r1 .iso and see if I can help with this.

[albfneto]

See what is strange...
More two retries...

freshly installed sabayon 4.0 r1, working!
rebooting, grub etc, working...
fluxbox ...
i tried ONLY:

Code: Select all

emerge --sync
emerge  portato (not emerge portage,for not dowgrade from2.2.17 to 1.2.6 series)


MANY PYTHON ERRORS...

I formatted partitions again... re install 4.0 r1, working, rebooting, again...
without portage...., fluxbox...
i made ONLY:

Code: Select all

equo update
equo install entropy
equo install equo sulfur
This installed or re-installed many packages (124), including, python and the new portage, 2-2-33.... as dependencies...


Closed, reboot etc....i dont updated kernel or NVIDIA....Rebboted and...

Compiz not works,different windows decorations, loose of these black window bars, of the 4.0 slow comp..., memory loss, commands? firefox no more works (im using epiphany)!!!
see the output of some simple commands:

Code: Select all

albfneto@localhost ~ $ firefox
Could not find compatible GRE between version 1.9.0.4 and 1.9.0.4.
albfneto@localhost ~ $ emerge -p krusader
Erro no barramento
albfneto@localhost ~ $ equo install krusader
Erro no barramento
albfneto@localhost ~ $
albfneto@localhost ~ $


Bus errors! seems no more compatibility... May be this part, the free space of my HDD, in witch i made the partions, that have bad clusters? Hardware problem?

[WarraWarra]

Problem:

emerge portato (not emerge portage,for not downgrade from 2.2.17 to 1.2.6 series)

Emerge / portage think you are in default x86 gentoo instead of default SL testing ~x86 tree that it should be.
Check:
nano /etc/make.conf
ACCEPTKEYWORDS="~x86"
If ~x86 = good then goto next steps below from 1 to 10 with gui gnome / kde or "nox" login.

NB> emerge --sync only after step 4 below for best results. Below = 97% - 99% success over 8 clean installs in 1 week.

Fresh install then do not first "emerge --sync"

Steps / method for best results after clean install.

Code: Select all

1. equo update
equo install equo entropy sulfur layman portage
equo conf update

2. equo search portage
portage 2.2.32 or 2.2.33 =  good.

3. layman -S
This tells portage / emerge to use the sabayon overlay / fixes / mods.

4. Now
emerge --sync

5. equo database gentoosync

6. equo world -p
or
equo world --fetch
equo world --multifetch=8
This will download all needed or group of 8 packages in 1 block / group.
 
7. equo world

8. equo conf update

9. equo libtest

10. equo deptest

ps> you can separate commands using the ;
example:
task 1 ; task 2 ; task 3
If 1 fails to start and complete then task 2 will start and complete or fail then task 3 start.

Alternative method:
task 1 && task 2 && task 3
This will start task 1 and complete or fail then all stop and fix then start over or continue if successful to task 2.

This installed or re-installed many packages (124), including, python and the new portage, 2-2-33.... as dependencies...

This is good and fine = correct.

Code: Select all

After python install always check before reboot if python = happy ?
# python-updater

Then always fix broken if broken or not fix it , there is always something that needs to be fixed.
# equo libtest
# equo deptest

After all this you can reboot and all should be fine.

I had to reinstall nvidia after update like this from clean install for best performance even if installed during update = seperate equo install nvidia-drivers nvidia-settings

PS> You can copy to usb hard drive /usr/portage folder and /var/lib/entropy folder to reuse with next install = most files needed = then on usb drive and copy back to /usr/portage or /var/lib/entropy after new install.

Always check commands spelling and correct use method in help files.
equo --help
layman --help
emerge --help

[joost]

albfneto I think you didn't properly migrate python.

Check with this:

Code: Select all

eselect list python

To get back about where this topic is about.

If you keep your system up2date with entropy you are Sabayon 4.2(beta)

[albfneto]

Still the same errors.
WarraWarra, during your precedure, when carry out your suggested commands, on a clean installation of 4.0 r1, again the same problems, even withou using portage, only entropy....

after the command:

Code: Select all

equo install equo entropy sulfur


the installation of packages or dependencies that changes the version o Phython, severe crashs the system..
Partition errors, BUS errors, extremely slow, totally unusable... it is not more possible made commands, as equo install something, emerge sommmething, even with the -p option, neither python-updater command;;; Message:
BUS Errors...
I have in mind that the newer python or the newer entropy are no more compatible with the 4.0r1;;;

See if i tried to update entropy prior installation:
i carried out, in the 4.0 r1 boot, on the DVD boot:

Code: Select all

su
cd /
cd /opt/anaconda
equo update


equo update changed to the new entropy......see, after "equo search entropy

Code: Select all

  @@ Package: sys-apps/entropy-0.95.8             branch: 4
>>        Available:            version: 0.95.8 ~ tag: NoTag ~ revision: 0
>>        Installed:            version: 0.95.8 ~ tag: NoTag ~ revision: 0
>>        Slot:                 0
>>        Homepage:             http://www.sabayonlinux.org
>>        Description:          Official Sabayon Linux Package
>>                              Manager library


But when i try to ru installer, a python library error:

Code: Select all

sabayonx86-64 anaconda # anaconda
Traceback (most recent call last):
  File "/opt/anaconda//usr/bin/anaconda", line 29, in <module>
    from constants import ANACONDA_PATH
  File "/opt/anaconda/usr/lib/anaconda/constants.py", line 20, in <module>
    from entropy import EquoInterface
ImportError: cannot import name EquoInterface
sabayonx86-64 anaconda #


Messages when tru to re install python , in the same DVD boot conditions, prior to install:

sabayonx86-64 anaconda # equo install python
>> @@ Calculating dependencies ...
>> @@ Packages needing to be installed/updated/downgraded: 3
>> @@ Packages needing to be removed: 0
>> @@ Download size: 12.5MB
>> @@ Freed disk space: 12.2MB
>> @@ You need at least: 12.7MB of free space
>> :: (1/3) >>> dev-lang/python-2.5.4-r2
>> ## Downloading archive: dev-lang:python-2.5.4-r2~0.tbz2
>> ## ( mirror #1 ) Downloading from: na.mirror.garr.it
>> ## ( mirror #1 ) Successfully downloaded from: na.mirror.garr.it at 138.8kB/second
>> ## Package checksum matches: dev-lang:python-2.5.4-r2~0.tbz2
>> :: (2/3) >>> sys-libs/ncurses-5.7
>> ## Downloading archive: sys-libs:ncurses-5.7~0.tbz2
>> ## ( mirror #1 ) Downloading from: na.mirror.garr.it
>> ## ( mirror #1 ) Successfully downloaded from: na.mirror.garr.it at 116.4kB/second
>> ## Package checksum matches: sys-libs:ncurses-5.7~0.tbz2
>> : SHA1 matches
>> : SHA256 matches
>> : SHA512 matches
>> :: (3/3) >>> dev-libs/openssl-0.9.8k
>> ## Downloading archive: dev-libs:openssl-0.9.8k~0.tbz2
>> ## ( mirror #1 ) Downloading from: na.mirror.garr.it
>> ## ( mirror #1 ) Successfully downloaded from: na.mirror.garr.it at 127.3kB/second
>> ## Package checksum matches: dev-libs:openssl-0.9.8k~0.tbz2
>> : SHA1 matches
>> : SHA256 matches
>> : SHA512 matches
>> ++ (1/3) >>> dev-lang/python-2.5.4-r2
>> ## Unpacking package: dev-lang:python-2.5.4-r2~0.tbz2
>> ## Ebuild: pkg_preinst()
>> ## Ebuild: pkg_prerm()
>> ## Ebuild: pkg_postrm()
* Linking /usr/bin/python2.5 to /usr/bin/python (relative)
* Linking /usr/bin/python2.5 to /usr/bin/python2 (relative)
* Linking /usr/bin/idle2.5 to /usr/bin/idle (relative)
* Linking /usr/bin/pydoc2.5 to /usr/bin/pydoc (relative)
* Linking /usr/bin/python-config-2.5 to /usr/bin/python-config (relative)
* Linking /usr/share/man/man1/python2.5.1.bz2 to /usr/share/man/man1/python.1.bz2 (relative)
* Cleaning orphaned Python bytecode from /usr/lib/python2.5 ..
* Cleaning orphaned Python bytecode from /usr/lib64/python2.5 ..
>> ## Installing package: dev-lang/python-2.5.4-r2
>> ## Updating database: dev-lang/python-2.5.4-r2
>> ## Cleaning old package files...
>> ## Ebuild: pkg_postinst()
* Linking /usr/bin/python2.5 to /usr/bin/python (relative)
* Linking /usr/bin/python2.5 to /usr/bin/python2 (relative)
* Linking /usr/bin/idle2.5 to /usr/bin/idle (relative)
* Linking /usr/bin/pydoc2.5 to /usr/bin/pydoc (relative)
* Linking /usr/bin/python-config-2.5 to /usr/bin/python-config (relative)
* Linking /usr/share/man/man1/python2.5.1.bz2 to /usr/share/man/man1/python.1.bz2 (relative)
* Byte compiling python modules for python-2.5 .. ... [ ok ]
* Byte compiling python modules for python-2.5 .. ... [ ok ]
* Byte compiling python modules for python-2.5 .. ... [ ok ]

*
* If you have just upgraded from an older version of python you will
* need to run:
*
* /usr/sbin/python-updater
*
* This will automatically rebuild all the python dependent modules
* to run with python-2.5.
*
* Your original Python is still installed and can be accessed via
* /usr/bin/python2.x.
*
>> ## Regenerating /etc/ld.so.cache
>> ## Updating {conf.d,init.d} mtime ...
>> ## Cleaning: dev-lang/python-2.5.4-r2
>> ++ (2/3) >>> sys-libs/ncurses-5.7
>> ## Unpacking package: sys-libs:ncurses-5.7~0.tbz2
>> ## Ebuild: pkg_prerm()
>> ## Ebuild: pkg_postrm()
>> ## Installing package: sys-libs/ncurses-5.7
>> ## Updating database: sys-libs/ncurses-5.7
>> ## Cleaning old package files...
>> ## Regenerating /etc/ld.so.cache
>> ## Regenerating /etc/ld.so.cache
>> ## Updating environment ...
>> ## Cleaning: sys-libs/ncurses-5.7
>> ++ (3/3) >>> dev-libs/openssl-0.9.8k
>> ## Unpacking package: dev-libs:openssl-0.9.8k~0.tbz2
>> ## Ebuild: pkg_preinst()
>> ## Ebuild: pkg_prerm()
>> ## Ebuild: pkg_postrm()
>> ## Installing package: dev-libs/openssl-0.9.8k
>> ## Updating database: dev-libs/openssl-0.9.8k
>> ## Cleaning old package files...
>> ## Ebuild: pkg_postinst()
>> ## Regenerating /etc/ld.so.cache
>> ## Cleaning: dev-libs/openssl-0.9.8k
>> @@ Installation complete.
>> @@ Caching complete.
sabayonx86-64 anaconda # python-updater
* Couldn't determine any previous Python version(s).
* Use -o OLD_PYTHON_VERSION to specify your old python version.
sabayonx86-64 anaconda # /usr/sbin/python-updater
* Couldn't determine any previous Python version(s).
* Use -o OLD_PYTHON_VERSION to specify your old python version.
sabayonx86-64 anaconda # eselect python list
!!! Error: Can't load module python
Died
sabayonx86-64 anaconda #

[albfneto]

Yesterday i used my not updated 4.0 r1, for writing the posts.
now i logged into the 4.2 update, same comp. i have multiple boot.
i have also two possibilities... using Xdelta,or "making" an Full 4.2 r', installing the packages of the 4.0 r1, all in new versions, over an working 4.1 GNOME or KDE or wanting from the 4.2 official version...

I continue to post here, since i consider the problem interesting for the developers and testers of the Sabayon Linux.

May be hardware related... This is an Athlon DX2, AMD 6000+, 64 bits.I have 2 HDDs, in one of then, master, i have the 4.0r1 Sabayon, not updated, 4.1 GNOME also with KDE 4.2.3, aon other graphical interfaces, fully updated until 4.2 beta ((Im using this boot at this moment) and also Mandriva 2009.1, Gentoo 2008 updated , and in the slave HDD i have Windows 7... and Arch Linux, all all fully operating,

including the 4.0 r1, in condition that is not updated, works. But even the automatic verification of the Entropy verification applet, i removed, because it caused... slower navigation after running....
As aditional information, i some triws i used only entropy, iin others only portage, all over a clean 4.0 r1 installation.

When i tried only with Portage, i used "Entropy's" Portage version, since the Gentoo's Portage new version is actually Hardmasked, but it is not the problem, since i use the hardmasked newer Portage in Gentoo itself...

Only if i install applications that not uses os changes Python, as krusader 1.9, Metisse, bui if i try to install equo, for example, or python, or portato or applications that uses python... and the comp installation turned problematic
including with Reiserfs partition errors.

This may be hardware related, since in the University, i have another comp, an Sempron 1800, in witch Sabayon 4.o r1 was installed in January, 2009, and from this, many updates were carried out, until now, and the comp is now a full 4.0 r1, fully updated to 4.2 beta, KDE 4.2.3, KDE 3, New GNOME, nex XFCE, new LXDE, new Python etc... including, some packs were updated with portage, example GCC 4.3.3... in this machine all working....!
Seems to me that something in one of my comps turns Python not more compatible..

The 4.2 versions are in my comps, also visualy better. the colors, the resolution the video 3D effects, are also brighter, more beautifull and faster.....

[albfneto]

I carried out, the full updating, with the lastest entropy, it works.
But now, is still turns much more slow in execution.
But accordinf with Wolfden, in this Forum, really the 4.0 r1 is too old tobe fully updated, and their python libraries are quite different.
Resuming, the fully updating is possible, but not so easy in some comps.
Seems to be better to install more packages, oven an 4.1 GNOME or KDE, previously updated to 4.2.
Briefly, the 4.2 official version, and further, the 5.0, will be released.

[albfneto]

In my experiments, in the new Entropy vesion, after the possibility of totally going to Python 2.6, GCC 4.4.0 and kernel 2.6.30...
Is it possible to transform totally the 4.0 r1, in a new , fully updated 4.2, Branch five...

Is it not an How-To is an experiment, not sure results in all comps, but i made this with sucess:

1) Install fresh the 4.0 r1, reboot, open it an small graphical env, as flux, then carried ou the these commands, (and some other eventually acessory commands as uname, for see if kernel, python etc... are the current versions):

Code: Select all

su
equo update
gedit /etc/entropy/repositories.conf, alter to get branch 5, save and close editor...then
equo update --force
equo world
use eselect and gcc-config to set kernel (30), python (2.6) and GCC (4.4.0)  to the last versions
reboot to the ney kernel 2.6.30, in the Grub, then
equo upgrade
equo install nvidia drivers
python -updater


TThis is the result: An totally updated 4.0 r1, all packages, with kernel 30,python 2.6, GCC 4.4.0. See:

http://i89.servimg.com/u/f89/13/49/51/58/captur18.png
http://www.angelfire.com/wa/brasbeto/sabanew.png