# ansible-galaxy role dependencies broken?

**URL:** <https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [January 3, 2014, 11:52am UTC](https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257 "2014-01-03T11:52:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raphael\_Randschau](https://avatars.discourse-cdn.com/v4/letter/r/c0e974/32.png) [@Raphael\_Randschau](https://forum.ansible.com/u/Raphael_Randschau)\
**Post date:** [January 3, 2014, 11:52am UTC](https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257/1 "2014-01-03T11:52:38Z")

</div>

Hey there,

I just realised that installing galaxy roles does not download the dependencies listed in the meta/main.yml.

Take for example one of my roles, rails-deployment: meta/main.yml does list my dependencies (which is properly formatted according to galaxy source:

[https://github.com/nicolai86/ansible-rails-deployment/blob/v0.3.2/meta/main.yml](https://github.com/nicolai86/ansible-rails-deployment/blob/v0.3.2/meta/main.yml)

but the api does NOT list my dependencies, thus failing to install them when installing the above role:

[https://galaxy.ansibleworks.com/api/v1/roles/105/dependencies](https://galaxy.ansibleworks.com/api/v1/roles/105/dependencies)

Is this a bug in ansible galaxy, is the galaxy source wrong, or is it a fault on my side? please advise.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [January 4, 2014, 2:38am UTC](https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257/2 "2014-01-04T02:38:31Z")

</div>

I’m getting a permission error actually. Are you getting this when visiting the dependency URL?

" “detail”: “You do not have permission to perform this action.”

This is almost definitely on our side, but let me know the above and I’ll get this queued up.

I know we tested some dependency things, so it’s probably just a question of why it’s returning the above 🙂

---

<div class="post-metadata">

**Author:** ![Raphael\_Randschau](https://avatars.discourse-cdn.com/v4/letter/r/c0e974/32.png) [@Raphael\_Randschau](https://forum.ansible.com/u/Raphael_Randschau)\
**Post date:** [January 10, 2014, 7:48am UTC](https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257/3 "2014-01-10T07:48:27Z")

</div>

I deleted my package and re-uploaded it to galaxy because I was trying to get it to properly parse my dependencies.  
My assumption was that maybe - since the source is closed - it would only properly parse dependencies the first time I import a package, and at that point in time the dependencies where NOT listed properly. But this was wrong.

The correct dependency URL is now

[https://galaxy.ansibleworks.com/api/v1/roles/](https://galaxy.ansibleworks.com/api/v1/roles/105/dependencies)156[/dependencies](https://galaxy.ansibleworks.com/api/v1/roles/105/dependencies)

(105 → 156)

But the issue remains. Any advice?

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [January 10, 2014, 1:56pm UTC](https://forum.ansible.com/t/ansible-galaxy-role-dependencies-broken/14257/4 "2014-01-10T13:56:45Z")

</div>

We’ve opened a ticket on role dependencies and will be taking a look at this – note that Galaxy is still in BETA mode and we’re working on quite a lot of improvements that we’re going to be releasing some each week for the next month or more.

For now, though, you’ll want to download the deps manually.