# Keeping old Ansible PPA repo versions **URL:** \ **Category:** Ansible Project\ **Created:** [March 26, 2015, 2:29pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850 "2015-03-26T14:29:01Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Rob\_Zienert](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@Rob\_Zienert](https://forum.ansible.com/u/Rob_Zienert)\ **Post date:** [March 26, 2015, 2:29pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/1 "2015-03-26T14:29:01Z")
With the regressions in 1.9.0 related to the s3 module[0], I think the Ansible package repos really need to keep more than the HEAD stable version in its versions list. When 1.9.0 was released yesterday, all of my company’s playbooks broke since we make extensive use of S3 - so right now we can’t do any deployments. I thought this would be an easy fix by version locking back to 1.8.4, but when I listed the versions in the apt repo, only 1.9.0.1 is available. While I plan to stay updated, I don’t want Ansible to dictate when I have to increment to a new minor (or major) version for exactly these kind of reasons. [0] [https://github.com/ansible/ansible-modules-core/issues/964](https://github.com/ansible/ansible-modules-core/issues/964) ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [March 26, 2015, 3:00pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/2 "2015-03-26T15:00:01Z")
The issue with 1.9.0 and 1.9.0.1 was caused by not being able to upload a file with the same version to pypy, initially an incomplete tarball was uploaded, once we realized the error and deleted it we were forced to change the version number to be able to release as pypy does not allow overwriting the distribution tarball or version reuse. Since our build systems are tied for all distributions this affected our .deb and .rpms also. ---
**Author:** ![Rob\_Zienert](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@Rob\_Zienert](https://forum.ansible.com/u/Rob_Zienert)\ **Post date:** [March 26, 2015, 3:06pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/3 "2015-03-26T15:06:48Z")
So, in a normal usecase, 1.8.4 would’ve remained available? My concern isn’t 1.9.0 vs 1.9.0.1, but that the last minor version is kept available. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [March 26, 2015, 3:12pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/4 "2015-03-26T15:12:39Z")
No, the 1.8.4 issue was not expected, we are looking into it, it seems that previous versions were just removed, 1.8.4 SHOULD remain available. ---
**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\ **Post date:** [March 26, 2015, 3:36pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/5 "2015-03-26T15:36:23Z")
\ We aren't purposefully removing the old packages from the PPA. It looks like the PPA is automatically marking the older packages as "superseded" and preparing to delete them when we upload a newer version: [https://launchpad.net/~ansible/+archive/ubuntu/ansible/+packages?field.name\_filter=&field.status\_filter=&field.series\_filter=](https://launchpad.net/~ansible/+archive/ubuntu/ansible/+packages?field.name_filter=&field.status_filter=&field.series_filter=) Do you (or anyone) happen to know if this is a configurable setting in Ubuntu PPA's? I think we'd be happy to change it but so far we haven't found if it's a configurable setting and if so where. -Toshio ---
**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:** [March 26, 2015, 3:41pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/6 "2015-03-26T15:41:16Z")
Ansible 1.8.4 is still available, we’ve just always had our pip settings configured to “hide” older releases. You can still install the older version by specifying it to pip: pip install ansible==1.8.4 ---
**Author:** ![Rob\_Zienert](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@Rob\_Zienert](https://forum.ansible.com/u/Rob_Zienert)\ **Post date:** [March 26, 2015, 4:00pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/7 "2015-03-26T16:00:33Z")
Okay, great. Thanks for the clarification, Brian. ---
**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\ **Post date:** [March 26, 2015, 4:11pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/8 "2015-03-26T16:11:16Z")
We still haven't been able to find a PPA setting to disable the auto delete (or to restore the previous version? There must be a toplevel menu for configuring PPAs that we just aren't seeing...). As a temporary solution you can grab the old .deb from here: [https://launchpad.net/~ansible/+archive/ubuntu/ansible/+build/6993788/+files/ansible\_1.8.4-1ppa~precise\_all.deb](https://launchpad.net/~ansible/+archive/ubuntu/ansible/+build/6993788/+files/ansible_1.8.4-1ppa%7Eprecise_all.deb) and then install it from the .deb during your provisioning. -Toshio ---
**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\ **Post date:** [March 26, 2015, 4:35pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/9 "2015-03-26T16:35:26Z")
After unsuccessfully looking around for instructions on the internet I took a look at what other PPAs were doing. I'm not a Ubuntu/Debian user but I wasn't able to find any PPAs that have multiple versions (there are packages for multiple ubuntu releases but not multiple versions of the package for a single release). If you're able to find out how to do it we'll be happy to change our PPA to keep multiple builds but it seems like this might not be a feature that Ubuntu's PPA service supports. ☹ -Toshio ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [March 26, 2015, 4:38pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/10 "2015-03-26T16:38:03Z")
apt repos allow this but as far as I can tell it does not work for PPAs, we can have diff package per arch or target distro .. but not sure if that will even be possible as a work around for this. ---
**Author:** ![Serge\_van\_Ginderacht](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@Serge\_van\_Ginderacht](https://forum.ansible.com/u/Serge_van_Ginderacht)\ **Post date:** [April 3, 2015, 5:38pm UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/11 "2015-04-03T17:38:38Z")
FYI A very nice project to organize and host apt repositories is aptly ([http://www.aptly.info/](http://www.aptly.info/)). It allows amongst other options to use Amazon S3, and has multiple options to organise multiple repositories, or repositories with and without multiple versions of packages etc. Might be more flexible than launchpad. Serge ---
**Author:** ![angel](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@angel](https://forum.ansible.com/u/angel)\ **Post date:** [May 31, 2016, 7:37am UTC](https://forum.ansible.com/t/keeping-old-ansible-ppa-repo-versions/17850/12 "2016-05-31T07:37:16Z")
Hi there, is there any update on this? One of our build pipelines is now stopped due to a bug in Ansible 2.1 that prevents artifacts to be downloaded from S3. I was surprised when I realised that Ansible 2.0.2.0 was not available anymore in the Ansible PPA. Thanks Angel