Summary: | sys-apps/portage-2.2.15 - CONFIG_PROTECT files which haven't changed are renamed anyway when config-protect-if-modified is not enabled in FEATURES (regression from 2.2.14) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andrew Church <achurch+gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS, REGRESSION |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 484436 |
Description
Andrew Church
2014-12-06 23:12:23 UTC
I suspect that your /etc/conf.d/pciparm is a symlink for some reason, and causes it to behave differently since the changes from bug #485598. $ ls -l /etc/conf.d/pciparm -rw-r--r-- 1 root root 988 Dec 7 08:05 /etc/conf.d/pciparm Also, this happens with all config files -- /etc/conf.d/pciparm was just an example (as it was the first file I noticed this problem with). I think I see the problem: https://github.com/gentoo/portage/commit/02417188225758b1822d176abd8902a92300a371 changed the meaning of FEATURES=-config-protect-if-modified from "protect unless file to be installed matches existing file, regardless of whether existing file has been changed from previously installed file" to "protect, always". If I enable config-protect-if-modified, the files are not backed up, as I would expect. If this is an intentional change then I suppose this bug is INVALID, though then I don't see a way to get the previous effect of disabling config-protect-if-modified (which is my desired setup). (In reply to Andrew Church from comment #4) > If this is an intentional change then I suppose this bug is INVALID, though > then I don't see a way to get the previous effect of disabling > config-protect-if-modified (which is my desired setup). It was not intended. It was just the unintended result of *lots* of changes. There's a patch in this branch: https://github.com/zmedico/portage/tree/bug_531854 I've posted it for review here: http://thread.gmane.org/gmane.linux.gentoo.portage.devel/4908 The patch works for me -- thanks for the quick fix! This is in the master branch now: https://github.com/gentoo/portage/commit/cea71687f6bbe0077d3c6271a39b15f6cc8bf325 Released in portage-2.2.16. |