1 |
On 2019.01.21 13:41, Jacques Montier wrote: |
2 |
> Le lun. 21 janv. 2019 à 19:19, Jack <ostroffjh@×××××××××××××××××.net> |
3 |
> a |
4 |
> écrit : |
5 |
> |
6 |
> > |
7 |
> > I have a suspicion that this really might be sandbox related. |
8 |
> > /dev/fd/whatever are all in the live system, and if I understand |
9 |
> > correctly, emerge works within the sandbox, so you should not be |
10 |
> able |
11 |
> > to get at those files (certainly not write to them, but it isn't |
12 |
> clear |
13 |
> > what the ebuild is trying to do there.) |
14 |
> > |
15 |
> > However, if you are running the emerge (please do clarify that your |
16 |
> are |
17 |
> > trying to emerge bash, not just manually build it) as root, I don't |
18 |
> see |
19 |
> > any reason it should try to use sudo for anything. |
20 |
> > |
21 |
> > Just for a change, try logging in as root, not doing su, and see if |
22 |
> the |
23 |
> > emerge works. |
24 |
> > |
25 |
> > Jack |
26 |
> > |
27 |
> |
28 |
> Jack, |
29 |
> - I don't manually build bash. Just : #emerge bash |
30 |
> - CTRL+Alt+F1 to get out of X and go to TTY1 |
31 |
> - logged as root with the root password |
32 |
> - emerge bash stops at password required. |
33 |
Since you are logged in as root, have you tried the root password when |
34 |
sudo asks? I wonder if it's looking for the portage password, which I |
35 |
don't think exists. As someone else said - there is really no reason |
36 |
for sudo to be used if you are root. However, during the emerge, I |
37 |
believe the effective UID is changed to portage. Does this give anyone |
38 |
else any further ideas of what to check? |