So I built Sabayon Core with XFCE. Somewhere along the way, Python got updated to 2.5.1-r2 and informed me that I had to run python-updater to re-emerge my Python apps. First, it kept saying it couldn't find certain ebuilds to emerge.. like subversion, etc. So I emerged them all manually.

Blocked packages.. some of them critical to the system, that can't be removed, and some that are co-existing, even though they're supposed to be blocked..?

What do I do from here? I can't update my python modules and none of my python applications work, including Porthole. I'm surprised portage even works since it's written in python. I can't seem to revert to 2.4.4 because then python-updater says it can't find a version to update?

Each package would already be in the world file though, these are all packages that have already been installed that need to be re-emerged. Still chugging along, working on glibc now..

No idea why it wants to go down to 2.4.4-r5 for Python. Again, friggin weird.

As I progress down the list (I'm emerging them in the order python-updater listed them) the reported "blocked" packages are actually disappearing each time python-updater -p is run... this is so odd. This system is pretty much vanilla too, I installed Sabayon Core, emerged xorg-x11, and emerged xfce..

edgevision wrote:Each package would already be in the world file though, these are all packages that have already been installed that need to be re-emerged. Still chugging along, working on glibc now..

Installed and "in world file" are not the same ... you never want libraries and stuff to be listed in the world file ...

As I type this, I'm re-installing Sabayon Core. A companion of mine (a Gentoo enthusiast) pointed out that python-updater wanted me to upgrade gcc-4.1.2 to 4.2.0... this would have broken a lot of packages and would be a huge waste of time. I'm giving it another go, and this time, I don't plan on updating my python past 2.4.4.. I guess my biggest question is, why. Why did updating my python break my system, and why when I follow the standard procedure for updating python did it want to emerge all of those packages?

I think that this is really a Sabayon problem. Me as a Gentoo User did not have any problem with python-updater, as I run "emerge -uNDav world" nearly once a day. Thus python-updater did not want to update anything but just did plain rebuilds.
In Sabayon you now have a problem as several critical updates fall together...

edgevision wrote:As I type this, I'm re-installing Sabayon Core. A companion of mine (a Gentoo enthusiast) pointed out that python-updater wanted me to upgrade gcc-4.1.2 to 4.2.0... this would have broken a lot of packages and would be a huge waste of time. I'm giving it another go, and this time, I don't plan on updating my python past 2.4.4.. I guess my biggest question is, why. Why did updating my python break my system, and why when I follow the standard procedure for updating python did it want to emerge all of those packages?

There are huge differences between the portage configuration on Core and regular installs, notably in make.conf and package.mask, as well as the world file. I'm going to assume these all played a part in what happened, but still, I should be able to upgrade Python on a fresh Core install of Sabayon without breaking the system.

This time around, I decided to install Sabayon with GNOME and then emerge XFCE afterwards. I would highly suggest that the dev team have a look at Core and how it functions. I'm using it on another server right now, luckily I never tried to upgrade python on that box so for now I'm adding >dev-lang/python to /etc/portage/package.mask.