Package managers won't launch [Solved]

[pscytzo]

Not sure where to post this... but my package managers aren't launching or running in CLI.

When i try to launch in GUI (using the e17 build of Sabayon, which i did get to upgrade to sabayon 10) i get this error:
Enlightenment was unable to run the application:
sulfer (or rigo)
The Application failed to start.


Then when i try to run it in terminal, nothing happens:

l4ap68 ~ # equo update
l4ap68 ~ # equo info
l4ap68 ~ # equo list
l4ap68 ~ # rigo info
l4ap68 ~ # rigo update
l4ap68 ~ # rigo
l4ap68 ~ #


So its looking like i have a hooched up install of my software management. This occured after i upgraded everything to Sabayon 10. I'm not even sure what log files to look at or watch. The /var/log/messages has a whole lotta nothing on this error.

Thanks in advance!
Let me know if i should move this post elsewhere!

[wolfden]

odd, if entropy is completely dead you can try reinstalling it from portage

emerge --sync
emerge entropy equo
equo update
equo upgrade
equo deptest

when doing updates it's best to make sure you always have the latest entropy installed first, so something like

Code: Select all

equo update && equo install entropy equo && equo upgrade && equo deptest

is a for sure way to make sure entropy gets bumped to latest first before doing upgrades and deptest is always a good thing to run to make sure all deps arrived. I use that command all time after I had a few issues of not updating entropy first.

[pscytzo]

Unfortunately i get the same reaction from portage also:

Code: Select all

l4ap68 ~ # emerge --sync
l4ap68 ~ #

Man i'm wondering what got horked-up.

[Fitzcarraldo]

Hmm... Python, perhaps?

[pscytzo]

Not sure... but i panzied out & just installed a fresh install of Sabayon 10 Mate. I'll try to slap a copy of the newest e17 on top of that then...

Thanks for the thoughts though!

[Joecanadian]

FWIW: I ran into exactly the same problem after an attempted upgrade to kernel 3.6 went off the rails, leaving the system with network, Xorg-server and python issues. For some reason -- in my defence, it was very late and I was horribly under-caffeinated -- I chose to unmask Python-3.2.3 and run python-update after the installation. Of course, that completely borked both equo and emerge.

Fortunately, I noticed that eselect python list showed python-2.7.3 listed (interestingly, the only item showing), but unselected. After using eselect to set python-2.7.3, equo came back to life and I was able to remove and re-mask python-3.2.3.

[wolfden]

python-updater is a portage command, do not run this on entropy system and yes python 3 * will break stuffs.