Summary: | app-emulation/virtualbox - with FEATURES=userpriv - fails to compile with 'Permission Denied' when kernel is compiled with umask 077 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Denis M. (Phr33d0m) <god> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | bkohler, dev-portage, patrick, rodrigo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Denis M. (Phr33d0m)
2013-09-22 15:56:26 UTC
As far as I know this issue started with virtualbox 4.2.18 only. Had no problems like that up until 4.2.16. Are we sure this is a new issue with virtualbox, and not a result of the new portage default of FEATURES=userpriv? If you disable userpriv or allow the kernel sources to be portage:portage readable, does the build succeed? Ben that is correct, if I disable userpriv everything compiles fine. If anyone else finds this bug, until it's fixed, (re)compile your kernels under `umask 022` (at least) or disable FEATURES=-userpriv @dev-portage could you give your opinion on this? FEATURES=userpriv shouldn't bring, as far as I understand, this type of error as the files are indeed readable by portage (-rw-r--r--). Is this a virtualbox issue or a portage one? Okay, this seems to be an invalid bug, or better said, a picnic issue. Using umask 077 (or anything that does not allow (at least) read permission to the portage group) for compiling the kernel is a user problem, not a portage nor virtualbox one. Apologies. |