I'm doing this:
- name: Ensure Google Protocol Buffers source downloaded
get_url: url=https://protobuf.googlecode.com/files/protobuf-2.5.0.tar.bz2
dest={{ tmp }}/protobuf.tar.bz2
which worked fine with 1.5 - but with 1.5.2 from PyPi, I now get this:
failed: [default] = {failed: true, item:
1.5.3 is in PyPi now and this contains some improvements to check
additional files and locations, let us know if you are still seeing any
problems.
(Ubuntu users may also wish to run update-ca-certs to get the latest files)
--Michael
On Wed, Mar 12, 2014 at 6:02 PM, dl...@phemi.com wrote:
Le lundi 10 mars 2014 19:23:45 UTC-4, Michael DeHaan a écrit :
Ansible 1.5.1 Release Notes
Finally, code that performs URL downloads of https:// URLs has been
upgraded to validate the certificates where possible, unless a new
parameter “validate_certs=no” is passed to the module. This
1.6 is the current development branch
On 11 March 2014 12:16, Makimoto Marakatti makim...@gmail.com wrote:
Hi
On the release dir, the new file reads:
ansible-1.6.tar.gz 10-Mar-2014 23:13 532K
I'm guessing this is a typo??
On Monday, 10 March 2014 23:23:45 UTC, Michael DeHaan wrote:
Hello everyone, we have updated 1.5.1 with a 1.5.2 to fix a bug in the apt
module as a result of the above.
Please apply 1.5.2 instead.
It should be available now and if we need to update any other modules, we
will do so quickly.
Thanks to everyone who reported things!
On Mon, Mar 10, 2014
completely missed that.
thanks!
On Tuesday, 11 March 2014 11:44:18 UTC, Michael DeHaan wrote:
The 1.5.1 tarball is there as well.
The 1.6 tarball there is not a release tarball, and is a build system
artifact that is a result of our CI and probably a wrong button press.
I'll have
Missed a cherry-pick on 1.5.2
The 1.5.2 tarball has been updated and the tag has been moved.
PyPi has been updated.
On Tue, Mar 11, 2014 at 9:00 AM, Michael DeHaan mich...@ansible.com wrote:
Hello everyone, we have updated 1.5.1 with a 1.5.2 to fix a bug in the apt
module as a result of the
If the pipe filter is not working in a way that it previously worked,
please file a bug and we will look into it.
On Tue, Mar 11, 2014 at 4:25 PM, j...@musicmetric.com wrote:
Hello,
Are there any plans to give users the option of re-enabling execution
via shell (for the pipe lookup module
Hello,
Are there any plans to give users the option of re-enabling execution via
shell (for the pipe lookup module in particular) or is it to be considered
officially wrong from now on? We're using something like:
macro_new_pass32: {{ lookup('pipe','cat /dev/urandom | tr -dc A-Za-z0-9 |
head
