| Summary: | sys-apps/portage-2.2.1 breaks kernel sources | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | gentoo |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | critical | ||
| Priority: | Normal | ||
| Version: | 2.2 | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log of failed emerge | ||
With FEATURES=userpriv, the ebuild runs as "portage" user and "portage" group. So, you may need to adjust ownership of files in some cases. Alternatively, you can remove userpriv from FEATURES:
echo 'FEATURES="${FEATURES} -userpriv -usersandbox"' >> /etc/portage/make.conf
*** This bug has been marked as a duplicate of bug 477664 ***
|
Created attachment 358382 [details] build.log of failed emerge After updating portage to version 2.2.1, virtualbox-modules fails to (re-)emerge. Looks like portage is messing up some permissions: Makefile:1418: .vmlinux.cmd: Permission denied ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make[3]: stat: include/config/auto.conf: Permission denied The complete build.log is attached. Reproducible on different machines. Before portage update virtualbox-modules emerges fine.