# My galaxy content has evaporated

**URL:** <https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 2, 2023, 5:48pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295 "2023-10-02T17:48:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\
**Post date:** [October 19, 2023, 6:14pm UTC](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295/3 "2023-10-19T18:14:31Z")

</div>

I fixed the ownership for utoddl a couple days ago and also cleaned up the extra namespaces based on this post [Strangeness with my \*tiny\* namespace.collection migration from old-galaxy to galaxy-ng](http://forum.ansible.com/t/strangeness-with-my-tiny-namespace-collection-migration-from-old-galaxy-to-galaxy-ng/1612)

The plugin metadata issue still remains though. I believe that is due to the galaxy-importer code complaining about problems with the collection and not sending back the data (which implies it wouldn’t successfully publish right now either).

---

_[View the full topic](https://forum.ansible.com/t/my-galaxy-content-has-evaporated/1295)._