after a gcc update I used emerge -eav system emerge -eav world to fix some problems. My /etc/sudoers got overwritten by the default file at the same time as the logfile for app-admin/sudo-1.8.18_p1 was created. $ portageq envvar CONFIG_PROTECT CONFIG_PROTECT_MASK /etc /etc/stunnel/stunnel.conf /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/maven-bin-3.3/conf /etc/ca-certificates.conf /etc/chromium/policies/managed/chrome-gnome-shell.json /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/opt/chrome/policies/managed/chrome-gnome-shell.json /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo Anything else we can test?
Created attachment 473978 [details] emerge --info
If you had previously installed app-admin/sudo with a binary package created with `quickpkg --include-config=y`, then that would do it if FEATURES=config-protect-if-modified is enabled (the default).
I had never "installed app-admin/sudo with a binary package created with `quickpkg --include-config=y`" nor has Josef. Best, JS.
Could not reproduce this bug with =app-admin/sudo-1.9.3_p1 Rather, I got the following message, and was able to use etc-update as usual to deal with the change: * IMPORTANT: config file '/etc/sudoers' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. This bug seems like it should be closed.
