1 |
On Wednesday 30 April 2008, reader@×××××××.com wrote: |
2 |
> "Mark Knecht" <markknecht@×××××.com> writes: |
3 |
> > eix-sync |
4 |
> > eix-test-obsolete |
5 |
> > emerge -pvDuN --with-bdeps=y world |
6 |
> > emerge -p --depclean |
7 |
> > emerge -pvDuN --with-bdeps=y world |
8 |
> > revdep-rebuild -p |
9 |
> > eix-test-obsolete |
10 |
> > |
11 |
> > Assuming everything is totally clean, or at least understood, now I |
12 |
> > change the profile and repeat the above tasks. |
13 |
> |
14 |
> What does it mean or what is called for if eix-test-obsolete returns |
15 |
> hundreds of packages? |
16 |
|
17 |
It means you need to trim the contents of /etc/portage/package* :-) |
18 |
|
19 |
You probably have hundreds of USE flags set in package.use that are |
20 |
already in make.conf, or entries in various files for packages that are |
21 |
no longer installed, just to give 2 random examples. |
22 |
|
23 |
eix-test-obsolete groups it's output with headings above each group. The |
24 |
heading tells you enough to decide if you can trim stuff or not |
25 |
|
26 |
> Installed packages with a version not in the database (or masked): |
27 |
> |
28 |
> [U] app-admin/eselect (1.0.2@07/21/06 -> (~*)1.0.11-r1): Modular |
29 |
> -config replacement utility |
30 |
|
31 |
This one os marked ~x86 in the tree. Possibly you explicitly merged it |
32 |
with an entry in package.keywords, then removed that entry later after |
33 |
merging the package. |
34 |
|
35 |
|
36 |
|
37 |
|
38 |
-- |
39 |
Alan McKinnon |
40 |
alan dot mckinnon at gmail dot com |
41 |
|
42 |
-- |
43 |
gentoo-user@l.g.o mailing list |