Summary: | emerge doesn't honor --config-root for /etc/portage/package.use/* | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robert White <rwhite> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | critical | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 484436 |
Description
Robert White
2015-03-17 18:11:45 UTC
What version of sys-apps/portage do you have? Maybe it's fixed by this commit, released in portage-2.2.16: http://gitweb.gentoo.org/proj/portage.git/commit/?id=417fc75190eb70836de9856f35c8141cacfd49fb (In reply to Zac Medico from comment #1) > What version of sys-apps/portage do you have? > > Maybe it's fixed by this commit, released in portage-2.2.16: > > http://gitweb.gentoo.org/proj/portage.git/commit/ > ?id=417fc75190eb70836de9856f35c8141cacfd49fb From initial description :: >> NOTE :: emerge --version >> Portage 2.2.17 (python 3.4.2-final-0, default/linux/amd64/13.0/desktop/kde, gcc-4.9.2, glibc-2.20-r2, 3.19.0-gentoo x86_64) Far more than a config protect or autowrite issue, when using --config-root=/somplace emerge doesn't consult /someplace/etc/portage/package.use, it only consults /etc/portage/package.use which it should not consult at all. I suspect that the other package.whatever directories/files are also affected. I am pretty sure that the entire subsystem was missed when CONFIG_ROOT was added as it's definitely picking the master set of configs instead of the target set. |