| 1 |
On 11/27/2011 02:34 PM, walt wrote: |
| 2 |
> Somewhere deep in the bowels of portage my 'introspection' useflag is |
| 3 |
> vanishing -- but on just one of my three machines. |
| 4 |
> |
| 5 |
> I set the introspection useflag on all three machines (two ~amd64 and |
| 6 |
> one ~x86) but when I run emerge --info, only two of the machines show |
| 7 |
> the introspection useflag in the output. |
| 8 |
> |
| 9 |
> All three machines share the same /usr/portage by NFS, so they all |
| 10 |
> see the same use.mask and use.force files, etc. |
| 11 |
|
| 12 |
Arrgh! Wrong! This is just as stupid as I knew it would be :( |
| 13 |
|
| 14 |
I started sharing portage over NFS last August, but on the problem |
| 15 |
machine I left /etc/make.profile pointing to the *old* repository on |
| 16 |
that machine, which hasn't been updated since August. |
| 17 |
|
| 18 |
I finally found the problem by running euse -a introspection and |
| 19 |
found it looking at the old profile instead of the fresh one. |
| 20 |
|
| 21 |
The relevant difference between the new and old profiles is that |
| 22 |
files like use.mask and package.use.mask have been updated to unmask |
| 23 |
the introspection useflag. |
| 24 |
|
| 25 |
For those interested in the gory details, portage was indeed reading |
| 26 |
the introspection useflag from my /etc/make.conf along with all my |
| 27 |
other useflags, but then the old profile was masking it out, leaving |
| 28 |
all my other useflag changes intact. That really fooled me. |
| 29 |
|
| 30 |
Thanks, Dale for all of your research. It prodded my fuzzy old brain |
| 31 |
into looking in different directions. |
| 32 |
|
| 33 |
Bill, your idea about the profile was right, but I thought you meant |
| 34 |
/etc/profile, not /etc/make.profile. <sigh> |
Archives