11.04.2016 17:09, Alan McKinnon wrote:
On 11/04/2016 15:15, Yuri K. Shatroff wrote:
Hi gentoo users,
Got a strange problem. While emerging kde-plasma/kscreenlocker (as part
of upgrading to the brand new plasma desktop), the build fails with the
following error:
* Applying kscreenlocker-5.4.90-no-SUID-no-GUID.patch ...
/var/tmp/portage/kde-plasma/kscreenlocker-5.6.2/temp/environment: line
1217:
/var/portage/tree/kde-plasma/kscreenlocker/files/kscreenlocker-5.4.90-no-SUID-no-GUID.patch:
Permission denied
I tried to run the ebuild manually and changed all permissions to a+w,
but to no avail. (The patch itself applied successfully from the command
line.)
I don't believe it's a permissions issue. There haven't been any such
issues before, and I just did a fresh eix-sync. Should I file a bug?
I have the same settings as you and kscreenlocker merges for me.
Alan, thanks for your quick reply!
Basic checks:
ls -al all the files in
/var/portage/tree/kde-plasma/kscreenlocker/files/ and parent
directories. Make sure they are OK, especially look for literal question
marks.
then run
"ebuild /var/portage/tree/kde-plasma/kscreenlocker/kscreenlocker-5.6.2
prepare"
and see what's at line 1217 of
/var/tmp/portage/kde-plasma/kscreenlocker-5.6.2/temp/environment plus a
few lines above and below.
This won't be executable permissions - ebuilds are sourced, not executed.
I suspect file corruption.
Actually, I started to panic too early. I logged into the `portage` user
and it turned out that the whole /var/portage/tree/kde-plasma directory
was inaccessible to it due to 0720 permissions (I have set up rsync to
use my own user and add g+w perms to `portage` group), but apparently
that dir had 0700 on the rsync mirror and g+w isn't just enough :)
So the problem was solved by chmod'ing the kde-plasma dir to g+rwx. As
usual, an easy solution is easily overlooked.
Sorry for the noise.
--
Regards,
Yuri K. Shatroff
