[SOLVED] Emerge --oneshot sys-apps/portage alters repos.conf

[davidbryant]

OK, I have suspected this for a while, but now I'm certain.

Whenever I install a new version of portage ("emerge --oneshot sys-apps/portage") it installs the configuration file /usr/share/portage/repos.conf. That's not supposed to happen. Emerge should update source code files and object code files, but it should leave user-maintained configuration files alone. We have dispatch-conf for that.

Here's a line from the latest install log.

Code: Select all

Installing /var/tmp/portage/sys-apps/portage-3.0.77-r3/work/portage-3.0.77-python3_13/cnf/repos.conf to /var/tmp/portage/sys-apps/portage-3.0.77-r3/image/usr/share/portage/config

Shall I report this as a bug? It's very annoying. I have to update the repos.conf file every time there's an update to portage.

[Hu]

I don't see that path as being under CONFIG_PROTECT, so it seems correct that Portage would overwrite it. Why do you think that is a user-maintained configuration file? If you want to override it, put your override in the appropriate path under /etc/portage.

[davidbryant]

Thank you, Hu.