| 1 |
On Sat, Jul 31, 2010 at 11:18 PM, Vaeth |
| 2 |
<vaeth@××××××××××××××××××××××××.de> wrote: |
| 3 |
> [I know that the headers are wrong; sorry for that] |
| 4 |
> |
| 5 |
>> I try the same on a relatively young gentoo server I'm managing and |
| 6 |
>> * dev-python/snakeoil |
| 7 |
>> Available versions: <yellow>~0.3.6.4 ~0.3.6.5 ~0.3.7</yellow> |
| 8 |
> [...] |
| 9 |
>> It's unkeyworded, however |
| 10 |
> As I understand, you already compared the output of eix --dump. |
| 11 |
> I suppose you verified that this output was created in the same |
| 12 |
> environment (i.e. with the same user and the same environment |
| 13 |
> variables) in which you call eix later on? |
| 14 |
Thanks for the user tip. |
| 15 |
|
| 16 |
I forgot that I "hardened" the server by default umasking all accounts |
| 17 |
to 007 (something I don't do on the desktop), so eix couldn't read the |
| 18 |
/etc/portage/ files as a regular user, because I wrote them as root. |
| 19 |
So if I eix as root or using sudo (which I don't do), I get the |
| 20 |
parens, but if I don't, eix can't read the keyword files, so no |
| 21 |
parens. Interesting. |
| 22 |
|
| 23 |
So this one's solved now. |
| 24 |
-- |
| 25 |
This email is: [ ] actionable [x] fyi [ ] social |
| 26 |
Response needed: [ ] yes [ ] up to you [ ] no |
| 27 |
Time-sensitive: [ ] immediate [ ] soon [ ] none |
Archives