1 |
On my Raspberry Pi2 (running Gentoo of cause) I have a problem with |
2 |
portage, or rather with emerge. When emerging something I get some error |
3 |
messages about "shell-init:... permission denied" like this: |
4 |
|
5 |
---------------------8<--------------------- |
6 |
>> Emerging (1 of 1) app-arch/xz-utils-5.2.2::gentoo |
7 |
shell-init: error retrieving current directory: getcwd: cannot access |
8 |
parent directories: Permission denied |
9 |
>>> Downloading 'http://distfiles.gentoo.org/distfiles/xz-5.2.2.tar.gz' |
10 |
--2016-03-26 16:31:48-- |
11 |
http://distfiles.gentoo.org/distfiles/xz-5.2.2.tar.gz |
12 |
Length: 1464228 (1.4M) [application/octet-stream] |
13 |
Saving to: ‘/usr/portage/distfiles/xz-5.2.2.tar.gz’ |
14 |
|
15 |
/usr/portage/distfi 100%[=====================>] 1.40M 3.06MB/s in |
16 |
0.5s |
17 |
|
18 |
2016-03-26 16:31:48 (3.06 MB/s) - |
19 |
‘/usr/portage/distfiles/xz-5.2.2.tar.gz’ saved [1464228/1464228] |
20 |
|
21 |
* xz-5.2.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... |
22 |
|
23 |
[ ok ] |
24 |
shell-init: error retrieving current directory: getcwd: cannot access |
25 |
parent directories: Permission denied |
26 |
shell-init: error retrieving current directory: getcwd: cannot access |
27 |
parent directories: Permission denied |
28 |
job-working-directory: error retrieving current directory: getcwd: |
29 |
cannot access parent directories: Permission denied |
30 |
chdir: error retrieving current directory: getcwd: cannot access parent |
31 |
directories: Permission denied |
32 |
>>> Unpacking source... |
33 |
>>> Unpacking xz-5.2.2.tar.gz to |
34 |
/var/tmp/portage/app-arch/xz-utils-5.2.2/work |
35 |
>>> Source unpacked in /var/tmp/portage/app-arch/xz-utils-5.2.2/work |
36 |
---------------------8<--------------------- |
37 |
|
38 |
The emerge continues and installs the software OK (as far as I can see). |
39 |
I tried to debug emerge (using --debug), but surprise surprise, just |
40 |
before the error messages shows there is a "set +x" in the output, hence |
41 |
I can not see which command it is that "produces" the error message and |
42 |
I can also not see the path/file that is the culprit. |
43 |
|
44 |
Any suggestions on how to debug this further? |
45 |
|
46 |
|
47 |
-- |
48 |
Dan Johansson, <http://www.dmj.nu> |
49 |
*************************************************** |
50 |
This message is printed on 100% recycled electrons! |
51 |
*************************************************** |