FYI
A very nice project to organize and host apt repositories is aptly (
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 flexi
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.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"An
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 fo
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/u
Okay, great. Thanks for the clarification, Brian.
On Thursday, March 26, 2015 at 10:12:57 AM UTC-5, Brian Coca wrote:
>
> 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.
>
>
>
> --
> Brian Coca
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
James Cammarata
Director, Ansible Core Engineering
github: jimi-c
On Thu, Mar 26, 2015 at 10
On Thu, Mar 26, 2015 at 7:29 AM, Rob Zienert wrote:
> 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 brok
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.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group a
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.
On Thursday, March 26, 2015 at 10:00:29 AM UTC-5, Brian Coca wrote:
>
> The issue with 1.9.0 and 1.9.0.1 was caused by not being able to
> upload a fi
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
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
11 matches
Mail list logo
