Or, at least, if you are going to try it, ensure that you have a binary package version of your current portage available, before you do. (If you are using FEATURES=buildpkg you should have one and know where it is. If not, quickpkg your current portage before attempting the upgrade.) If worse comes to worse, you can then untarbz2 it directly over your live installation to get a working portage back, altho you may have to use FEATURES=-sandbox, since sandbox is now a separate package.
At least... 20-r1 really borked me over, here, and I had to use the emergency portage recovery procedure with a copy of the previous binary package as above, to get a working portage again. http://bugs.gentoo.org/show_bug.cgi?id=90135 Note that ppc/osx opened a bug on it just before mine, 90133, tho with a bit different errors, as well, so it doesn't look to be amd64 only, but perhaps many of the non-x86_32 archs, having issues. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
