Summary: | How do I disable touch/chown of *.portage_lockfile? [Errno 1] Operation not permitted: b'/home/jeroen/portage/.dev-python.portage_lockfile': chown('/home/jeroen/portage/.dev-python.portage_lockfile', -1, 250) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kripton |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeroen Roovers (RETIRED)
![]() The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=89de8064e8d186a7a001dd1f2f5c486c64f4104f commit 89de8064e8d186a7a001dd1f2f5c486c64f4104f Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-12-31 05:23:29 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-12-31 05:25:06 +0000 locks: chown lockfiles only if permitted (bug 674090) Reported-by: Jeroen Roovers <jer@gentoo.org> Bug: https://bugs.gentoo.org/674090 Signed-off-by: Zac Medico <zmedico@gentoo.org> lib/portage/locks.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) I think that one commit should suppress all of the error messages shown in comment #0. Thanks! OK, so it was not a configuration error on my side. I've experienced this with portage-2.3.60 when using a DISTFILES folder mounted via SSHFS. Reverting to portage-2.3.51-r1 fixed it for me. (In reply to jannis from comment #4) > I've experienced this with portage-2.3.60 when using a DISTFILES folder > mounted via SSHFS. Reverting to portage-2.3.51-r1 fixed it for me. Please report a separate issue for SSHFS. (In reply to Zac Medico from comment #5) > (In reply to jannis from comment #4) > > I've experienced this with portage-2.3.60 when using a DISTFILES folder > > mounted via SSHFS. Reverting to portage-2.3.51-r1 fixed it for me. > > Please report a separate issue for SSHFS. Reported as bug 678218. |