1 |
Alan McKinnon <alan.mckinnon@×××××.com> writes: |
2 |
|
3 |
|
4 |
[...] |
5 |
|
6 |
>> -p --depclean tells me: |
7 |
>> |
8 |
>> !!! You have no system list. |
9 |
>> |
10 |
>> What does that mean? |
11 |
> |
12 |
> Trouble, big trouble. |
13 |
> |
14 |
> Does /etc/make.profile point to an actual existing profile? That's the |
15 |
> only thing I can think of that takes system away. It's defined in the |
16 |
> various files named "packages" in the profile directories. |
17 |
|
18 |
Yes it pointed to 2007 and was set with eselect profile set |
19 |
But anyway emerge tells you immediately when there is no profile. |
20 |
|
21 |
But there is good news... and it harks back to your second post on |
22 |
this monster thread: |
23 |
|
24 |
[...] |
25 |
|
26 |
Harry wrote: |
27 |
>> One blockage that looks to be particularly troublesome is: |
28 |
>> Portage blocking bash |
29 |
>> |
30 |
>> bash blocking portage. |
31 |
|
32 |
Alan replied: |
33 |
> That's a nasty one and you quite rightly don't want to unmerge portage |
34 |
> or bash. The trick is to do it in several stages: |
35 |
> |
36 |
> First look at portage: |
37 |
|
38 |
[...] |
39 |
|
40 |
|
41 |
> Recent portages want any bash >=bash-3.2_p17, but you can't use the most |
42 |
> recent bash (3.2_p33) as that blocks the portage you have. So, do it |
43 |
> manually: |
44 |
> |
45 |
> 1. emerge --nodeps bash-3.2_p17-r1 |
46 |
> 2. emerge --nodeps portage |
47 |
> 3. emerge bash |
48 |
> 4. emerge world |
49 |
> |
50 |
> The --nodeps is there to stop portage updating other stuff that |
51 |
> conflicts with what you are trying to do. |
52 |
> |
53 |
> Once this is done, you will still have the python/python-updater blocker |
54 |
> to deal with, but I seem to recall posting on that earlier |
55 |
|
56 |
That list error occurred prior to getting your above suggestion done. |
57 |
At that point emerge -vup system or really an emerge -u showed a |
58 |
about 12-15 blockages including portage and bash |
59 |
|
60 |
Once I followed the recipe above all that disappeared along with the |
61 |
list error. I think that older version of portage was really what |
62 |
was causing most of the trouble. |
63 |
|
64 |
At this point I have profile set to 2008-server and have completed an |
65 |
eix-sync with that profile active. I've now also trimmed the use list |
66 |
in make.conf down removing any x related ones and only using a few I |
67 |
know I want and a few left from the prior list that looked harmless. |
68 |
Also added a few `-' ones to be sure. (I hate maildir for example.) |
69 |
|
70 |
grep USE /etc/make.conf: |
71 |
|
72 |
USE=" -arts -X -xorg -maildir |
73 |
mbox emacs logrotate readline samba smb usb zlib |
74 |
|
75 |
Some may be redundant there.. but I doubt any will get me in trouble. |
76 |
|
77 |
I've test run emerge -vuDNp world and see no blockages. |
78 |
|
79 |
I'd like to get rid of a bunch of X stuff but not really sure how best |
80 |
to go at it. I really don't want to set thru the grinding of kde and |
81 |
really don't want X at all on this vmware. |
82 |
|
83 |
Would it work to that end if I edit the world file removing x related |
84 |
apps before running emerge -vuDNp world and with the new use flags in |
85 |
place. |
86 |
|
87 |
Or will that leave herds of stuff on board? |
88 |
|
89 |
-- |
90 |
gentoo-user@l.g.o mailing list |