Alan McKinnon <[EMAIL PROTECTED]> writes:
[...] >> -p --depclean tells me: >> >> !!! You have no system list. >> >> What does that mean? > > Trouble, big trouble. > > Does /etc/make.profile point to an actual existing profile? That's the > only thing I can think of that takes system away. It's defined in the > various files named "packages" in the profile directories. Yes it pointed to 2007 and was set with eselect profile set But anyway emerge tells you immediately when there is no profile. But there is good news... and it harks back to your second post on this monster thread: [...] Harry wrote: >> One blockage that looks to be particularly troublesome is: >> Portage blocking bash >> >> bash blocking portage. Alan replied: > That's a nasty one and you quite rightly don't want to unmerge portage > or bash. The trick is to do it in several stages: > > First look at portage: [...] > Recent portages want any bash >=bash-3.2_p17, but you can't use the most > recent bash (3.2_p33) as that blocks the portage you have. So, do it > manually: > > 1. emerge --nodeps bash-3.2_p17-r1 > 2. emerge --nodeps portage > 3. emerge bash > 4. emerge world > > The --nodeps is there to stop portage updating other stuff that > conflicts with what you are trying to do. > > Once this is done, you will still have the python/python-updater blocker > to deal with, but I seem to recall posting on that earlier That list error occurred prior to getting your above suggestion done. At that point emerge -vup system or really an emerge -u showed a about 12-15 blockages including portage and bash Once I followed the recipe above all that disappeared along with the list error. I think that older version of portage was really what was causing most of the trouble. At this point I have profile set to 2008-server and have completed an eix-sync with that profile active. I've now also trimmed the use list in make.conf down removing any x related ones and only using a few I know I want and a few left from the prior list that looked harmless. Also added a few `-' ones to be sure. (I hate maildir for example.) grep USE /etc/make.conf: USE=" -arts -X -xorg -maildir mbox emacs logrotate readline samba smb usb zlib Some may be redundant there.. but I doubt any will get me in trouble. I've test run emerge -vuDNp world and see no blockages. I'd like to get rid of a bunch of X stuff but not really sure how best to go at it. I really don't want to set thru the grinding of kde and really don't want X at all on this vmware. Would it work to that end if I edit the world file removing x related apps before running emerge -vuDNp world and with the new use flags in place. Or will that leave herds of stuff on board? -- [email protected] mailing list
