On Wednesday 13 May 2009 16:49:52 Stroller wrote: > I reread Alexey's post after replying to yours, and the reason he's > having problems is because he's being careless. If you break the > system, it's obviously a gamble whether you'll get your ass out of the > problem you created for yourself. If you want to be sure of not > breaking the system then you have to be cautious, resolve EACH and > EVERY dependency in turn and not just go "fukkit, i don't know what > that package does so, i'll ignore or unmerge it, upgrade this other > package to the latest version and hope everything resolves".
Very true. I see he's got the bash/portage mutual blocker one as well. Nasty one that - only by close study of the ebuilds did I manage to figure out that - upgrade bash to interim version in the tree - upgrade portage to latest - upgrade bash to latest was the only way through. In those days we didn't have automatic blocker resolution in portage either. And yes, if Alexey is being careless then portage is going to bite his ass. Alexey, if you read this: Do not unmerge bash, portage, wget or python without first making a quickpkg. Otherwise you will be left with an unusable system and no way out of it - portage uses those packages directly and cannot function without them. -- alan dot mckinnon at gmail dot com
