Summary: | ROOT=/build/ emerge -u ... doesn't do config file protection | ||
---|---|---|---|
Product: | Portage Development | Reporter: | echtler |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gent_bz, stefan |
Priority: | High | Keywords: | InVCS |
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 137867, 136244 | ||
Attachments: |
fix broken paths in the merge phase
fix ROOT=/ config protect breakage |
Description
echtler
2006-01-28 03:08:31 UTC
I have this same problem, even with $ROOT/etc (and others) in CONFIG_PROTECT. same problem here, is there any work-around? This should be working in 2.1. If it's not working in 2.1 or the latest ~arch release then please reopen. It seems like the problem isn't fixed yet. Tested with portage-2.1-r1, a customized ${ROOT}/etc/nsswitch.conf is overwritten every time I 'ROOT=/myroot emerge -k glibc'. When I chroot into /myroot an 'emerge -k glibc' the nsswitch.conf is protected and an etc-update list's an update. The problem is not related only to glibc but that's an example. Created attachment 91422 [details, diff]
fix broken paths in the merge phase
More than just config file protection is broken. Apparently, protected file destined for $ROOT are actually merged to / (extremely bad). This is fixed in svn r3836.
I wouldn't recommend for anyone to use $ROOT without the attached patch. This has been released in 2.1.1_pre2-r7. Created attachment 91558 [details, diff] fix ROOT=/ config protect breakage The first patch has a bug for ROOT=/ (see bug 140045). |