I was used to file issues on GitHub ansible/galaxy projects, but from New Ansible Galaxy - #12 it looks like issues should be opened here now. I tried to copy the content of the report Roles namespace has changed with the new Galaxy website · Issue #3253 · ansible/galaxy · GitHub here, but new user…

[image] btravouillon: looks like issues should be opened here now. You are correct! Thanks for the detailed output - I know the Galaxy team are triaging and working through the issues as fast as they can.

Hi, Is there any update on this issue?

I have confirmed that the issue being tracked here Loading... and being fixed here github_user should override namespace.name for legacy roles. by jctanner · Pull Request #1923 · ansible/galaxy_ng · GitHub will resolve the issues with the mila role installs. (venv) [jtanner@p1 galaxy_ng.legacy_role…

Alright, it seems better today. The erroneous role namespace is now empty. I guess this will be deleted in a near future. The only issue left is the avatar used in our role namespace which is not our logo but the profile picture of GitHub user mila. (which would be a real issue to me if my own face…

The only issue left is the avatar used in our role namespace which is not our logo but the profile picture of GitHub user mila. This is one of challenges of having a namespace on galaxy that matches some other user on github. We should never have created a namespace with that conflict considerin…

[image] tannerjc: This is one of challenges of having a namespace on galaxy that matches some other user on github. We should never have created a namespace with that conflict considering the user has been on github since 2009 https://api.github.com/users/mila and the namespace request was made …

But even then, this would have become an issue as soon as someone registered that user on GitHub. So, checking before creating a namespace would have been by no means a guarantee that there is no conflict. I agree. The only way to be certain the namespace had no conflicts would be for the role au…

[image] I think this issue as originally described is resolved. We also have ways to make uploads to various namespaces much easier now. [image] Ansible Galaxy’s role import enhancements and fixes for the new year Project Discussions Ansible Galaxy’s role import enhance…

Roles namespace has changed with the new Galaxy website

Get Help

gwmngilfen (Greg Sutcliffe) Split this topic October 3, 2023, 3:04pm 3

4 posts were split to a new topic: User ownership for namespace is getting changed to a different user

Topic		Replies	Views
Lost namespace's access Get Help galaxy-ng	6	410	October 22, 2023
Data migration to the new galaxy.ansible.com Get Help galaxy-ng , namespace , bug	10	777	November 12, 2023
Namespaces and remotes are messed up since the update Get Help galaxy-ng	6	324	November 9, 2023
Unable to import roles anymore: namespace different from github organization Get Help galaxy-ng , role	18	529	February 7, 2024
Namespace issue with new galaxy.ansible.com Get Help galaxy-ng	9	657	November 10, 2023

Roles namespace has changed with the new Galaxy website

Related topics