Summary: | sys-apps/portage: die due to ebuild permissions with FEATURES=userpriv should give a hint about userpriv | ||
---|---|---|---|
Product: | Portage Development | Reporter: | BRULE Herman <alpha_one_x86> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
BRULE Herman
2014-12-04 15:00:19 UTC
(In reply to BRULE Herman from comment #0) > /usr/lib64/portage/bin/ebuild.sh: line 545: > /usr/portage/x11-base/xorg-drivers/xorg-drivers-1.15.ebuild: Permission > denied For FEATURES=userpriv, you need to use the allow_other option when mounting fuse filesystems. We could fix portage to detect this case and give a more helpful error message. (In reply to Zac Medico from comment #1) > We could fix portage to detect this case and give a more helpful error > message. I guess we could simply improve the die message so that it gives a hint about userpriv. Yes, more information about use FEATURES=userpriv (if needed and not defaulted). allow_other information is usefull, but: curlftpfs#ftp://172.16.0.45/ /usr/portage/distfiles fuse rw,relatime,user_id=0,group_id=0,allow_other 0 0 Remain doing: bash: /mnt/system/portage/distfiles/.__portage_test_write__: Operation not supported Traceback (most recent call last): File "/usr/lib64/portage/pym/portage/util/_async/ForkProcess.py", line 45, in _spawn rval = self._run() File "/usr/lib64/portage/pym/_emerge/EbuildFetcher.py", line 172, in _run allow_missing_digests=allow_missing): File "/usr/lib64/portage/pym/portage/package/ebuild/fetch.py", line 646, in fetch wantnewlockfile=1, **lock_kwargs) File "/usr/lib64/portage/pym/portage/locks.py", line 105, in lockfile myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) File "/usr/lib64/portage/pym/portage/__init__.py", line 259, in __call__ rval = self._func(*wrapped_args, **wrapped_kwargs) OSError: [Errno 95] Operation not supported: '/mnt/system/portage/distfiles/.linux-3.14.tar.xz.portage_lockfile' * Fetch failed for 'sys-kernel/gentoo-sources-3.14.24', Log file: * '/mnt/system/tmp-disk/portage/sys-kernel/gentoo-sources-3.14.24/temp/build.log' (In reply to BRULE Herman from comment #3) > Yes, more information about use FEATURES=userpriv (if needed and not > defaulted). > allow_other information is usefull, but: > > curlftpfs#ftp://172.16.0.45/ /usr/portage/distfiles fuse > rw,relatime,user_id=0,group_id=0,allow_other 0 0 > Remain doing: > bash: /mnt/system/portage/distfiles/.__portage_test_write__: Operation not > supported FEATURES=userfetch is relevant for DISTDIR. > OSError: [Errno 95] Operation not supported: > '/mnt/system/portage/distfiles/.linux-3.14.tar.xz.portage_lockfile' You can use FEATURES="-distlocks" to avoid this. I don't have found this info with google. Then as portage output will be greate. -distlocks -ebuild-locks, remain this error on this output but continue to work: bash: /mnt/system/portage/distfiles/.__portage_test_write__: Operation not supported (In reply to BRULE Herman from comment #5) > bash: /mnt/system/portage/distfiles/.__portage_test_write__: Operation not > supported I guess this is because it tries to open __portage_test_write__ in append mode, and apparently curlftpfs does not support append mode. |