1 |
11.04.2016 17:09, Alan McKinnon wrote: |
2 |
> On 11/04/2016 15:15, Yuri K. Shatroff wrote: |
3 |
>> Hi gentoo users, |
4 |
>> |
5 |
>> Got a strange problem. While emerging kde-plasma/kscreenlocker (as part |
6 |
>> of upgrading to the brand new plasma desktop), the build fails with the |
7 |
>> following error: |
8 |
>> |
9 |
>> * Applying kscreenlocker-5.4.90-no-SUID-no-GUID.patch ... |
10 |
>> /var/tmp/portage/kde-plasma/kscreenlocker-5.6.2/temp/environment: line |
11 |
>> 1217: |
12 |
>> /var/portage/tree/kde-plasma/kscreenlocker/files/kscreenlocker-5.4.90-no-SUID-no-GUID.patch: |
13 |
>> Permission denied |
14 |
>> |
15 |
>> I tried to run the ebuild manually and changed all permissions to a+w, |
16 |
>> but to no avail. (The patch itself applied successfully from the command |
17 |
>> line.) |
18 |
>> I don't believe it's a permissions issue. There haven't been any such |
19 |
>> issues before, and I just did a fresh eix-sync. Should I file a bug? |
20 |
> |
21 |
> I have the same settings as you and kscreenlocker merges for me. |
22 |
|
23 |
Alan, thanks for your quick reply! |
24 |
|
25 |
> Basic checks: |
26 |
> |
27 |
> ls -al all the files in |
28 |
> /var/portage/tree/kde-plasma/kscreenlocker/files/ and parent |
29 |
> directories. Make sure they are OK, especially look for literal question |
30 |
> marks. |
31 |
> |
32 |
> then run |
33 |
> "ebuild /var/portage/tree/kde-plasma/kscreenlocker/kscreenlocker-5.6.2 |
34 |
> prepare" |
35 |
> |
36 |
> and see what's at line 1217 of |
37 |
> /var/tmp/portage/kde-plasma/kscreenlocker-5.6.2/temp/environment plus a |
38 |
> few lines above and below. |
39 |
> |
40 |
> This won't be executable permissions - ebuilds are sourced, not executed. |
41 |
> I suspect file corruption. |
42 |
|
43 |
Actually, I started to panic too early. I logged into the `portage` user |
44 |
and it turned out that the whole /var/portage/tree/kde-plasma directory |
45 |
was inaccessible to it due to 0720 permissions (I have set up rsync to |
46 |
use my own user and add g+w perms to `portage` group), but apparently |
47 |
that dir had 0700 on the rsync mirror and g+w isn't just enough :) |
48 |
|
49 |
So the problem was solved by chmod'ing the kde-plasma dir to g+rwx. As |
50 |
usual, an easy solution is easily overlooked. |
51 |
|
52 |
Sorry for the noise. |
53 |
|
54 |
-- |
55 |
Regards, |
56 |
Yuri K. Shatroff |