| 1 |
On 2018.06.26 15:44, Christoph Böhmwalder wrote: |
| 2 |
> On Tue, Jun 26, 2018 at 03:15:09PM -0400, Andrew Udvare wrote: |
| 3 |
> > It should not be accessing this location in any case. What is the |
| 4 |
> environment like? What does env show? emerge --config output? |
| 5 |
> > |
| 6 |
> > It would almost seem like you have $HOME set to /home/christoph |
| 7 |
> while Portage is running (as root). |
| 8 |
> |
| 9 |
> The only thing that stands out about `env` is that XDG_CONFIG_HOME is |
| 10 |
> set to /home/christoph/.config (running as root). I'm not sure if |
| 11 |
> it's supposed to be this way, but I didn't find anything in my |
| 12 |
> dotfiles that would suggest that I'm overwriting it. |
| 13 |
That's a normal setting for you. The problem is that when you did sudo |
| 14 |
or su to run emerge, it simply stayed in the environment, causing this |
| 15 |
problem. When you su or sudo to run emerge (or just log in directly as |
| 16 |
root) you need to be sure to do so in a way that cleans out your |
| 17 |
environment. I keep thinking to file a bug to request emerge to |
| 18 |
sanitize the environment, or at least add an option to make it do so. |
| 19 |
I often forget to use them, but I created scripts (cleanemerge and |
| 20 |
cleanebuild) to do that for me. |
| 21 |
> |
| 22 |
> $HOME points to /root. |
| 23 |
> |
| 24 |
> I'm not sure what you mean by "emerge --config output"? Running |
| 25 |
> `emerge --config` just gives: |
| 26 |
> |
| 27 |
> # emerge --config nodejs |
| 28 |
> |
| 29 |
> Configuring pkg... |
| 30 |
> |
| 31 |
> Warning: ccache requested but no masquerade dircan be found in |
| 32 |
> /usr/lib*/ccache/bin |
| 33 |
> * pkg_config() is not defined: 'nodejs-8.11.1.ebuild' |
| 34 |
> |
| 35 |
> |
| 36 |
> -- |
| 37 |
> Regards, |
| 38 |
> Christoph |
| 39 |
> |
| 40 |
> |
| 41 |
Jack |
Archives