A repo was renamed and now there is a collision everytime it is imported

[chouseknecht]

From @030 on January 23, 2017 9:29

030.rabbitmq was renamed to 030.ansible-sensu-client

 Error saving role: duplicate key value violates unique constraint "main_role_namespace_36aa1070a7d8dc70_uniq" DETAIL: Key (namespace, name)=(030, rabbitmq) already exists.
Error saving role: duplicate key value violates unique constraint "main_role_namespace_36aa1070a7d8dc70_uniq" DETAIL: Key (namespace, name)=(030, rabbitmq) already exists. 

Copied from original issue: ansible/galaxy-issues#232

[robertdebock]

I'm having a similar issue.

Galaxy reports:

Starting import: task_id=381113, repository=robertdebock/ansible-role-python_pip

===== LINTING ROLE: python_pip =====
yamllint OK.
ansible-lint OK.

Updating repository name "ansible-role-python_pip" -> "python_pip"
===== IMPORTING ROLE: python_pip =====
Adding role metadata tags
Adding role platforms

Task "381113" failed: duplicate key value violates unique constraint "main_repository_provider_namespace_id_name_8d721418_uniq" DETAIL: Key (provider_namespace_id, name)=(3967, python_pip) already exists.

To reproduce it: (I hope I remember correctly...)

1. Create a role, upload it to GitHub and import it.
2. Change the GitHub repository name.
3. Import the role again

[staticdev]

Is there any solution for it?