My Unofficial Guide to a Stable System World Update

[calvinthomas]

Just wanna say great guide! I'm not going to use it because I'm not experienced enough to be able to go through the problems and fix but for those who are I'm sure this is brilliant! We need more guides like this for Sabayon. Well done!

Calv

[schivmeister]

wolfden: that should be the update right? because for -e i get 1100+- packages since its like a stage 1 re-install..and that's after 5 hours of udept, removing apps, and world file trimming. Update i get 150+-..should be ok since i removed some.

[dragon_788]

Sadly this process isn't going very well on my fresh install of Sabayon 3.3 x64 edition on my Core 2 Duo laptop. The hardware recognition of Sabayon rocks, but so far I haven't had any success upgrading to the latest version of world. Are there any plans for the Sabayon devs to actually comment their package.mask configurations so we know WHY exactly something is masked?

[wolfden]

wolfden: that should be the update right? because for -e i get 1100+- packages since its like a stage 1 re-install..and that's after 5 hours of udept, removing apps, and world file trimming. Update i get 150+-..should be ok since i removed some.

Correct

[navman]

I'm not sure what to do here . I'm trying to get it to world update and it gives me this

09:54:08 (62.68 KB/s) - `/usr/portage/distfiles/liblazy-0.1.tar.bz2' saved [244241/244241]

* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
* checking liblazy-0.1.tar.bz2 ... [ !! ]

!!! Digest verification failed:
!!! /usr/portage/distfiles/liblazy-0.1.tar.bz2
!!! Reason: Failed on MD5 verification
!!! Got: c1adbf3fbe371bec9530e2c57514ea4c
!!! Expected: 22670656d849ab9c971d28ce3bfd884e

I even unpacked it and installed it with make but no good. Help please!!

[WarraWarra]

* Success:
* ------
*
* Successfully synchronized overlay "sabayon".
* Successfully synchronized overlay "einit".
* Successfully synchronized overlay "portato".
*
* Errors:
* ------
*
* The source of the overlay "einit" seems to have changed. You currently sync from "http://einit.svn.sourceforge.net/svnroot/einit/trunk/distro/gentoo/portdir_overlay" while the global layman list reports "http://svn.berlios.de/svnroot/repos/einit/trunk/distro/gentoo/portdir_overlay" as correct location. Please consider removing and readding the overlay!

On mini 3.3

[wolfden]

if you don't use einit - remove it

layman -d einit

if want still want it afterwards

layman -a einit

[flick]

I'm using 3.3 x86_64 mini on an HP dv6000, Turion 64 dual core with an Nvidia card.

Just did a fresh install, ran the script to emerge the kernel sources. Emerged udept and ran dep -w to clean up the world file. Have not run emerge --sync. Did run layman -d einit to remove that overlay as I have no interest in using einit, and emerge -C mozilla-thunderbird for the same reason.

I plan to use emerge -pe system and emerge -pe world after I recompile the kernel and change the use flags ( really just the cflags, to match my cpu ). In theory, that will warn me of upcoming issues, yes?

And yeah, I'm well aware I could still hose the system -- hence doing it on a clean install.

Does it sound like I'm on the right track, if I follow Wolfden's guide closely and listen to portage?

[wolfden]

yup you sound like you are

[flick]

Did emerge -e system. Went fine up till it tried emerging python. Then my machine made a loud continuous beep, the screen froze, I couldn't even switch to a different virtual terminal. Rebooted...and the system won't boot. Typing this while using the livecd and doing a fresh install. Anyone else seen this particular hiccup?