# Ansible RPM version

**URL:** <https://forum.ansible.com/t/ansible-rpm-version/15214>\
**Category:** Ansible Project\
**Created:** [May 12, 2014, 7:17pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214 "2014-05-12T19:17:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tracy\_Phillips](https://avatars.discourse-cdn.com/v4/letter/t/df705f/32.png) [@Tracy\_Phillips](https://forum.ansible.com/u/Tracy_Phillips)\
**Post date:** [May 12, 2014, 7:17pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/1 "2014-05-12T19:17:04Z")

</div>

I was just about to install Ansible using EPEL and it seems to be behind in release version, currently, it is at 1.5.5. Does Ansible (the company) maintain this RPM?

I don’t mind building 1.6 from the .spec file but since I have EPEL being pulled into Spacewalk, it would make it a lot easier to maintain if EPEL were current.

---

<div class="post-metadata">

**Author:** ![nirik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nirik/32/686_2.png) [@nirik](https://forum.ansible.com/u/nirik)\
**Post date:** [May 12, 2014, 7:22pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/2 "2014-05-12T19:22:46Z")

</div>

> I was just about to install Ansible using EPEL and it seems to be  
> behind in release version, currently, it is at 1.5.5. Does Ansible  
> (the company) maintain this RPM?

Nope. 🙂

I usually update it within hours of release, but EPEL has a policy for  
updates that requires updates to either:

a) Spend 2 weeks in epel-testing

or

b) get +3 karma from 3 people who the update worked for.

Before it goes to updates.

See: [https://admin.fedoraproject.org/updates/ansible/](https://admin.fedoraproject.org/updates/ansible/)

> I don't mind building 1.6 from the .spec file but since I have EPEL  
> being pulled into Spacewalk, it would make it a lot easier to  
> maintain if EPEL were current.

1.6.1 is in epel-testing and has been since right after it was  
released.

Karma welcome.

kevin

---

<div class="post-metadata">

**Author:** ![Tracy\_Phillips](https://avatars.discourse-cdn.com/v4/letter/t/df705f/32.png) [@Tracy\_Phillips](https://forum.ansible.com/u/Tracy_Phillips)\
**Post date:** [May 12, 2014, 7:30pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/3 "2014-05-12T19:30:03Z")

</div>

Thanks Kevin, I will install it from testing and throw some karma your way.

---

<div class="post-metadata">

**Author:** ![Strahinja\_Kustudic2](https://avatars.discourse-cdn.com/v4/letter/s/b4bc9f/32.png) [@Strahinja\_Kustudic2](https://forum.ansible.com/u/Strahinja_Kustudic2)\
**Post date:** [June 7, 2014, 8:46pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/4 "2014-06-07T20:46:00Z")

</div>

Would be awesome to have an official Ansible repository, like [yum.ansible.com](http://yum.ansible.com) 🙂

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [June 8, 2014, 1:14am UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/5 "2014-06-08T01:14:41Z")

</div>

We are planning on doing this at some point in the (hopefully near) future, for both yum and apt.

---

<div class="post-metadata">

**Author:** ![C\_Morgan\_Hamill](https://avatars.discourse-cdn.com/v4/letter/c/ebca7d/32.png) [@C\_Morgan\_Hamill](https://forum.ansible.com/u/C_Morgan_Hamill)\
**Post date:** [June 9, 2014, 12:17pm UTC](https://forum.ansible.com/t/ansible-rpm-version/15214/6 "2014-06-09T12:17:01Z")

</div>

Excerpts from James Cammarata's message of 2014-06-07 21:14:41 -0400:

> We are planning on doing this at some point in the (hopefully near) future,  
> for both yum and apt.

Not entirely on-topic, but it's a "thing" of mine:

Thank you all \*so much\* for having functioning distribution packages  
from a very early stage in Ansible. As someone who falls way more on  
the "ops" than the "dev" side of things, it's refreshing to see projects  
with actual release processes and proper packaging, which in these heady  
Github days are all too often omitted.
