Summary: | root login or su - required to install dev-libs/cyrus-sasl-2.1.26-r9(r10) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | B Nice <Anonymous_Pseudonym_88> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | major | CC: | openhs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
B Nice
2016-05-20 12:39:36 UTC
It sounds like you may have some bad permissions on /usr/portage/distfiles/cyrus-sasl-2.1.26.tar.gz. Make sure the portage user has read access to this file. I wouldn't think it should make any difference as it's the sudo user who's permissions should matter, but here is the ls -las 5100 -rw-rw-r-- 1 portage portage 5220231 Feb 22 2013 /usr/portage/distfiles/cyrus-sasl-2.1.26.tar.gz The other files in the folder have the exact same permissions and install using sudo emerge with no issues. (In reply to B Nice from comment #2) > I wouldn't think it should make any difference as it's the sudo user who's > permissions should matter, but here is the ls -las The unpack phase always runs as the portage user when the userpriv feature is enabled. This package unpacks without an issue using sudo on my system. This is probably a configuration problem somewhere on your system; maybe you have some odd environment variable set, or some resource limit is killing the tar process. It may be, but there are a number of people who are having the same issue who probably don't have the same configuration. https://forums.gentoo.org/viewtopic-t-944432-highlight-cyrussasl.html In fact out of four systems I have running Gentoo, only one has the issue. The only thing that is out of the norm for the system with this issue, is that it is a pure ~amd64 system. Could it be due to an unstable bzip or tar? I'm going to wager a guess that either a resource limit or memory is being exceeded. That is possible. I only have 8GB of RAM and 16GB of swap, so it may have exceeded the space available to non-root users. Since I don't have a quota system set-up on this machine, this e-build managed to do what libreoffice and firefox builds couldn't. It may be worthwhile to contact the other people on the forum thread to see what their system set-ups are like. I've Solved This Issue By Re-Building (On Another Computer - with 'buildpkg' FEATURE Turned-On) & Re-Installing (The Resulting Binary Package...) a Few Packages : tar gzip bzip2 xz-utils bash ( <- This One Seem To Have Actually Caused This Issue ) * Also, I've Deleted PORTAGE Temp. Dir. ( e.g. : /var/tmp/portage ) - Thus Enabling a Clean Re-Creation of It By PORTAGE' "emerge". *** Bug still appears. I've stumbled upon it during profile switch to 17.0 while doing emerge -e @world via ssh then 'su -'. Using sudo, or screen session did not work either. Running emerge from remote graphical emacs (eshell) worked for me. dev-libs/cyrus-sasl-2.1.26-r9 app-arch/tar-1.29-r3 app-arch/gzip-1.8 CFLAGS="-O2 -march=core-avx-i -mcx16 -msahf -maes -mpclmul -mpopcnt -mavx -msse4 .2 -msse4.1 -mfsgsbase -mrdrnd -mf16c --param l1-cache-size=32 --param l1-cache- line-size=64 --param l2-cache-size=3072 -fweb -pipe" CXXFLAGS="${CFLAGS}" Stable amd64 system. |