I just emerged portage-2.0.51.20 (part of emerge -u world) on two of my systems, and each one reported "X config files in /etc need updating." etc-update reports the following: # etc-update Scanning Configuration files... Exiting: Nothing left to do; exiting. :) It exits with rc=0. Looks like something got b0rked within etc-update .
Same here. ciaranm@snowdrop ~ 0 0.31 $ find /etc/ -name '.*cfg*' /etc/._cfg0000_dispatch-conf.conf /etc/._cfg0000_make.conf.example ciaranm@snowdrop ~ 0 0.13 $ sudo /usr/sbin/etc-update Scanning Configuration files... Exiting: Nothing left to do; exiting. :)
This directory is not in CONFIG_PROTECT so it is not scanned?
Yes, thers is NO /etc in CONFIG_PROTECT. Here is mine: CONFIG_PROTECT="/usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" There is no CONFIG_PROTECT in make.globals. Emerging baselayout just wiped out all my configs in /etc because of this! I noticed it only after env-update said there is nothing to update. BTW, is it possible that portage-2.0.51.20.tar.bz2 is not complete? If you compare it to portage-2.0.51.19.tar.bz2 you'll see that the directory cnf does not contain arch-specific make.globals while they were present in 2.0.51.19. Hope you put /etc in CONFIG_PROTECT as soon as possible or many more people will have to restore their configuration from backup...
CONFIG_PROTECT has been updated in the profiles. It will hit the rsync mirrors in about 20 minutes (if it's not there already). Yes, it was my fault for forgetting to add these, but why didn't anybody add these (at least to base) when it was first found?
Damn, seems I sync'd my tree too early :-) Anyway, I've added CONFIG_PROTECT="/etc" to my make.conf just for the case something similar happens again. Maybe it's worth mentioning somewhere (newsletter?) as a trivial safeguard.
