On Wed, Dec 16, 2020 at 11:57:49PM -0800, Onno wrote:
...snip...
>
> Is my understanding correct that CentOS 7 is EOF jan 2020 if you want
> Python3? Python3 implies CentOS 8 or higher?
Well, I think it's more nuanced than that. CentOS/RHEL7 now does have
python3.6 shipped with it, but of course
On Thu, 3 Nov 2016 13:32:54 -0700 (PDT)
Jacob Weber wrote:
> Just curious -- how long does it usually take for new RPMs to appear
> on epel or epel-testing?
https://groups.google.com/forum/#!msg/ansible-project/dm59ern73-w/SaBIVJAeBjAJ
kevin
--
You received this message because you are subscr
On Sat, 19 Mar 2016 05:51:32 -0700 (PDT)
George Khan wrote:
> Hi all!
> I ask it jan 18, and ask after 2 month: Any news about ansible2 in
> debian8/centos7 _stable_ repo? :)
If you mean the epel7 repo there, it's likely we will wait for 2.1 to
come out. In particular a lot of people seem to be
On Sat, 10 Oct 2015 11:28:24 -0700 (PDT)
J Hawkesworth wrote:
> I think I read somewhere on the EPEL site that it is usually about 2
> weeks. I guess there might be a little more time to wait for mirrors
> to catch up too.
>
> Jon
>
I wrote about this a while back:
https://groups.google.co
On Fri, 20 Feb 2015 22:34:27 -0600
James Cammarata wrote:
> Hi Walter.
>
> No, we usually do not, since each distro packages the release at
> their own speed and we don't keep track of them all. I know for EPEL,
> it's usually about 2-3 weeks for the package to make its way out of
> the testing
On Wed, 15 Oct 2014 21:01:55 -0400
Todd Zullinger wrote:
> With pipelining = True commented out on el6, things still fail for me
> on the first run. They do fail with a different error, but perhaps
> that's just due to slightly different code paths with pipelining on
> and off, I haven't look
On Wed, 15 Oct 2014 16:07:42 -0700
Michael DeHaan wrote:
> "I think this is a bug, has anyone tested this ?"
>
> Sounds like this should be reported with RHEL, definitely.
>
> Please do and post the bugzilla here if you can.
>
> While we could add special code to say "don't try CP on EL6 if ss
On Tue, 9 Sep 2014 19:17:03 -0700 (PDT)
Jacob Weber wrote:
> Is there a place to download an ansible 1.7.1 RPM? I can only find
> version 1.7 on epel and epel-testing, and that has a bad bug with
> commands that have a lot of output. I can no longer find 1.6.x in
> epel either, so I'm kind of stu
On Mon, 12 May 2014 15:17:04 -0400
Tracy Phillips wrote:
> 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 ha
On Fri, 31 Jan 2014 20:26:43 -0800 (PST)
David Peterka wrote:
> Do like this:
>
> user_data"#!/bin/bash\nsleep 10"
>
> you can pass python style \n newlines.
Well, one of the things I tried was:
user_data="#cloud-config\ndisable_root: 0"
But that didn't seem to get to the instance either. ;
Greetings.
I find myself wanting to pass some user_data to a call to the ec2
module, but I am unclear on the format I should be passing it.
Basically I want to pass it:
#cloud-config
disable_root: 0
When I call the ec2 module, what exactly do I give user_data= ?
I tried various formats of
't mention vars as being reserved. ;(
I got it working... something was wacky with my git checkout I was
running from. I did a clean checkout and reconverted and everything
seems to be working now.
Thanks and sorry for the noise.
kevin
--
>
>
>
> On Wed, Jan 1, 201
Greetings.
I'm running into something weird with vars_files and I thought I would
ask the list if it's a bug I should file or if I am just doing
something wrong. ;)
I had:
vars_files:
- /srv/web/infra/ansible/vars/global.yml
- $private/vars.yml
- $vars/$ansible_distributiion.yml
Just thought I would send a short note to the list about epel and
fedora packages for those that are using them. There seems to be a bit
of confusion about when they are available, etc.
- I've been building new ansible versions into all supported Fedora
branches and epel-6 usually within an hou
14 matches
Mail list logo