Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 258829 - hardcodes CONFIG_PROTECT="-*"
Summary: hardcodes CONFIG_PROTECT="-*"
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Reported: 2009-02-13 09:40 UTC by Oleh Kravchenko
Modified: 2010-02-24 23:20 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info (,3.85 KB, text/plain)
2009-02-14 13:22 UTC, Oleh Kravchenko

Note You need to log in before you can comment on or make changes to this bug.
Description Oleh Kravchenko 2009-02-13 09:40:12 UTC
When I updating base packages, configuration in /etc/conf.d set to default :(


Reproducible: Always
Comment 1 Allen Brooker (AllenJB) 2009-02-13 10:23:21 UTC
This is likely unrelated to etc-update, but to Portage's internal config handling. Check the output of "emerge --info | grep PROTECT"

CONFIG_PROTECT tells portage to not automatically replace files in the given directories, so they get handled by etc-update or dispatch-conf. CONFIG_PROTECT_MASK allows you to then tell Portage that certain locations within CONFIG_PROTECT should have their files automatically replaced (so they don't get handled by etc-update or dispatch-conf).

If you're still having problems, please post the full output of "emerge --info" and describe which options you're using in etc-update.
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2009-02-13 14:29:26 UTC
The real problem is Portage's --noconfmem (or the absence thereof in default EMERGE_DEFAULT_OPTS) as it causes necessary (e.g. incompatible) config file changes to be disregarded. I did never care to look, if this feature simply buggy or conceptually broken, but changed it in make.conf locally.

A proper version of a feature to deal with config files changes transparently would store a hash of the installed "vanilla" config files sans comments and do a comparison, if the config file (again: sans comments) coming with a newer ebuild differs to it (instead the user modified config file) to deduct, if it may be necessary to pester a human with it.
Comment 3 Zac Medico gentoo-dev 2009-02-13 19:01:49 UTC
(In reply to comment #0)
> When I updating base packages, configuration in /etc/conf.d set to default :(

As said in comment #1, please post CONFIG_PROTECT and CONFIG_PROTECT_MASK settings. Perhaps you've got CONFIG_PROTECT="-*"?

(In reply to comment #2)
> The real problem is Portage's --noconfmem

I haven't seen anything in comment #0 to suggest that --noconfmem is relevant to this bug, since confmem deals with things not being merged rather than config protection.

Comment 4 Oleh Kravchenko 2009-02-14 13:22:55 UTC
Created attachment 181998 [details]
emerge --info
Comment 5 Oleh Kravchenko 2009-02-14 13:35:59 UTC
Overwriting /etc/conf.d files happens when I call bootstraping

$ /usr/portage/scripts/
$ emerge -e world
Comment 6 Zac Medico gentoo-dev 2009-02-14 18:30:42 UTC
(In reply to comment #5)
> Overwriting /etc/conf.d files happens when I call bootstraping
> $ /usr/portage/scripts/
> $ emerge -e world

I don't know where you got the idea to call, but it has CONFIG_PROTECT="-*" hardcoded internally.
Comment 7 Zac Medico gentoo-dev 2009-02-15 02:04:28 UTC
Since bug #247776, there's already a warning produced by emerge when CONFIG_PROTECT is empty.

Reassigning to base-system in case they want to change the behavior of with respect to CONFIG_PROTECT.
Comment 8 SpanKY gentoo-dev 2009-02-15 02:20:05 UTC
i dont see the point.  dont run on a stage3+.  if it breaks, you get the pieces.
Comment 9 Oleh Kravchenko 2009-02-15 06:55:06 UTC
I am porting gentoo on my pda. So i need bootstrap :)

details about pda here
Comment 10 SpanKY gentoo-dev 2009-02-15 18:19:22 UTC
that is irrelevant.  bootstrap is run natively on the device by catalyst.  if you run it by hand, you better know what you're doing (including clobbering of config files).