This seems extreme for one package named "tree", when Pagure's web UI has a similar bug https://pagure.io/pagure/issue/4409
What if we just set the policy to "If your package is on the list of names at https://docs.gitlab.com/ee/user/reserved_names.html , add a "-pkg" suffix" ?
Does the GitLab support contract cover this sort of thing?
- Ken
On Tue, Aug 31, 2021 at 7:35 AM Florian Weimer fweimer@redhat.com wrote:
Gitlab cannot support an undocumented set of Git repository names. Currently, this list appears to contain at least these names:
badges blame blob builds commits create create_dir edit files find_file new preview raw refs tree update wikisThere may be additional constraints for:
environments gitlab-lfs infoWe have at least one collision today, tree.
One way to avoid these problems is to prefix all package names with “pkg-”. This way, future collisions become extremely unlikely, at the cost of a one-time large rename.
The alternative would be to main an exception mechanism for colliding package names such as “tree”. This has been the current approach, but as far as I can tell, it is not working.
Implementing this change depends on the completion of the package removal process because it does not appear worthwhile to rename packages which no longer exist in the distribution.
Thanks, Florian
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel