| Summary: | sys-apps/portage-2.3.59: emerge fails with IOError: [Errno 1] Operation not permitted | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Jean-Francois Ostiguy <jfostiguy> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | Keywords: | InVCS, REGRESSION |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 658182, 671498 | ||
|
Description
Jean-Francois Ostiguy
2019-01-29 17:40:44 UTC
Ensure you have CONFIG_PID_NS in your kernel. If not, enable it or set FEATURES="-pid-sandbox" for the time being The issue is actually fixed in sys-apps/portage-2.3.59-r1, but you'll have to use FEATURES="-pid-sandbox" if you currently have sys-apps/portage-2.3.59 installed. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=d66f4238e6b5dca2bbc0fb04f64c67f3e0bc3586 commit d66f4238e6b5dca2bbc0fb04f64c67f3e0bc3586 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2019-01-28 19:27:47 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2019-01-28 19:42:21 +0000 pid-sandbox: handle EnvironmentError for python2 compat (bug 675868) The fcntl.ioctl call raises IOError, which is different from OSError for python2. Use EnvironmentError for compatibility. Bug: https://bugs.gentoo.org/675868 Reported-by: Ivan Ivanich <ivanich@ivanich.org.ua> Fixes: ce0656337268 ("pid-sandbox: pid-ns-init TIOCSCTTY after setsid (bug 675868)") Signed-off-by: Zac Medico <zmedico@gentoo.org> bin/pid-ns-init | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a89abbf82cc13d266d512b3100bb990ed7718f40 commit a89abbf82cc13d266d512b3100bb990ed7718f40 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2019-01-28 19:41:43 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2019-01-28 19:47:08 +0000 sys-apps/portage: revbump to 2.3.59-r1 for bug 675868 Bug: https://bugs.gentoo.org/675868 Reported-by: Ivan Ivanich <ivanich@ivanich.org.ua> See: https://gitweb.gentoo.org/proj/portage.git/commit/?id=d66f4238e6b5dca2bbc0fb04f64c67f3e0bc3586 Package-Manager: Portage-2.3.59, Repoman-2.3.12 Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-apps/portage/{portage-2.3.59.ebuild => portage-2.3.59-r1.ebuild} | 3 +++ 1 file changed, 3 insertions(+) This issue was first reported in bug 675868, comment 18. I'm using sys-apps/portage-2.3.59-r1, -pid-sandbox does not help.
Traceback (most recent call last):
File "/usr/lib/portage/python3.6/socks5-server.py", line 231, in <module>
asyncio.start_unix_server(s.handle_proxy_conn, sys.argv[1], loop=loop))
File "/usr/lib64/python3.6/asyncio/base_events.py", line 468, in run_until_complete
return future.result()
File "/usr/lib64/python3.6/asyncio/streams.py", line 151, in start_unix_server
return (yield from loop.create_unix_server(factory, path, **kwds))
File "/usr/lib64/python3.6/asyncio/coroutines.py", line 212, in coro
res = func(*args, **kw)
File "/usr/lib64/python3.6/asyncio/unix_events.py", line 290, in create_unix_server
sock.bind(path)
PermissionError: [Errno 13] Permission denied
However, it does not stop emerge, just distcc fails.
(In reply to Saul Peebsen from comment #4) > I'm using sys-apps/portage-2.3.59-r1, -pid-sandbox does not help. > > Traceback (most recent call last): > File "/usr/lib/portage/python3.6/socks5-server.py", line 231, in <module> > asyncio.start_unix_server(s.handle_proxy_conn, sys.argv[1], loop=loop)) > File "/usr/lib64/python3.6/asyncio/base_events.py", line 468, in > run_until_complete > return future.result() > File "/usr/lib64/python3.6/asyncio/streams.py", line 151, in > start_unix_server > return (yield from loop.create_unix_server(factory, path, **kwds)) > File "/usr/lib64/python3.6/asyncio/coroutines.py", line 212, in coro > res = func(*args, **kw) > File "/usr/lib64/python3.6/asyncio/unix_events.py", line 290, in > create_unix_server > sock.bind(path) > PermissionError: [Errno 13] Permission denied > > However, it does not stop emerge, just distcc fails. That's unrelated to bug 676856, you have an issue with FEATURES=network-sandbox-proxy there. I haven't seen any reports like that, please file a new bug. (In reply to Zac Medico from comment #5) > (In reply to Saul Peebsen from comment #4) > > I'm using sys-apps/portage-2.3.59-r1, -pid-sandbox does not help. > > > > Traceback (most recent call last): > > File "/usr/lib/portage/python3.6/socks5-server.py", line 231, in <module> > > asyncio.start_unix_server(s.handle_proxy_conn, sys.argv[1], loop=loop)) > > File "/usr/lib64/python3.6/asyncio/base_events.py", line 468, in > > run_until_complete > > return future.result() > > File "/usr/lib64/python3.6/asyncio/streams.py", line 151, in > > start_unix_server > > return (yield from loop.create_unix_server(factory, path, **kwds)) > > File "/usr/lib64/python3.6/asyncio/coroutines.py", line 212, in coro > > res = func(*args, **kw) > > File "/usr/lib64/python3.6/asyncio/unix_events.py", line 290, in > > create_unix_server > > sock.bind(path) > > PermissionError: [Errno 13] Permission denied > > > > However, it does not stop emerge, just distcc fails. > > That's unrelated to bug 676856, you have an issue with > FEATURES=network-sandbox-proxy there. I haven't seen any reports like that, > please file a new bug. Completely unrelated to this bug, but in case someone comes across the Permission denied issue the cause for me was the PORTAGE_TMPDIR wasn't writable by portage (usually portage writes to PORTAGE_TMPDIR/portage, which was writable) |
