Although aliases can be assigned to repositories, either by the user or by repositories themselves, these cannot be used as the [name] in repos.conf. This is inconvenient if a repository wants to change its name without breaking existing configurations. I have already fixed this, I'm just filing this bug for posterity.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=ea04a583fab9739dbe05e8d8381ed2803e7dce88 commit ea04a583fab9739dbe05e8d8381ed2803e7dce88 Author: James Le Cuirot <chewi@gentoo.org> AuthorDate: 2024-07-09 13:07:58 +0000 Commit: James Le Cuirot <chewi@gentoo.org> CommitDate: 2024-07-10 16:55:20 +0000 config: Allow a repository to be configured using one of its aliases Currently, the `[name]` in repos.conf can only match the primary name. This is inconvenient if a repository wants to change its name without breaking existing configurations. This raises the question of whether to then use the primary name or the alias in the UI and in the vardb. I went with the primary name because this is presumably the name that the repository actually wants you to use. If the configured name matches neither the primary name nor an alias, then emaint sync will simply claim that it is not found, but that behaviour is unchanged from before. Bug: https://bugs.gentoo.org/935830 Closes: https://github.com/gentoo/portage/pull/1358 Signed-off-by: James Le Cuirot <chewi@gentoo.org> NEWS | 3 +++ lib/portage/repository/config.py | 10 ++++++---- 2 files changed, 9 insertions(+), 4 deletions(-)
