Package Details: ansible-git v2.7.0.a1.r3199.g2721ed260e-1

Git Clone URL: (read-only)
Package Base: ansible-git
Description: Radically simple IT automation platform
Upstream URL:
Licenses: GPL3
Conflicts: ansible, python-ansible
Provides: ansible, python-ansible
Replaces: ansible, python-ansible
Submitter: l3u
Maintainer: Thermi
Last Packager: brenix
Votes: 22
Popularity: 0.000000
First Submitted: 2012-04-19 14:00
Last Updated: 2019-02-10 02:49

Dependencies (20)

Required by (11)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Svenstaro commented on 2019-03-24 16:44

Now needs to optdep on hcloud-python for hcloud support.

rubdos commented on 2018-06-20 18:32

Could you please change to CHANGELOG.rst?

wknapik commented on 2018-06-08 16:24

Hi. I flagged the package out of date, but that's not correct.

There might be some issues with installing/updating/deleting when changing between ansible and ansible-git packages. Or it could be something weird that only happened on my system...

Sorry for the false alarm.

brenix commented on 2018-05-29 15:23

@actionless: I've added ansible back in the provides array. Thanks for the heads up!

actionless commented on 2018-05-29 14:42

it's missing Provides: ansible

can be a problem when installing, let's say, ansible-lint commented on 2018-05-26 13:37

install: cannot stat '': No such file or directory
==> ERROR: A failure occurred in package().

The README file is called README.rst.

UPDATE: There also no

wknapik commented on 2017-11-15 12:24

@brenix: this is a -git package, so you're checking out the git repo anyway, so it shouldn't be a problem to source hacking/env-setup, right ? Why not do that ? Or do whatever env-setup does to generate the version ?

brenix commented on 2017-11-10 19:21

@wknapik: The version being reported through the ansible cli looks at the git repository information to display that version. Since packages built with makepkg typically don't (and shouldn't) include the .git directory, this is why it can't determine the git branch/details and falls back to the major version. If this is still desired, then I would recommend using a local checkout and sourcing the hacking/env-setup file. We can look into updating the pkgver function, but that still wont affect the output of `ansible --version`

wknapik commented on 2017-11-09 11:24

Hi. `ansible --version|head -n1' always returns "ansible 2.5.0", regardless of which revision you're on. I hear regular/manual builds off devel return something like "ansible 2.5.0 (devel 843fba509f) last updated 2017/11/02 12:11:53 (GMT +100)". This is a problem, especially when reporting issues in ansible, where they ask you to paste the output of `ansible --version' and it doesn't actually say what version you're using.

mikky commented on 2017-09-12 21:15

allright, the is not compatible with latest Python 3 due to absense of sys.maxint. One must force Python2.

Simply add this line to your PKGBUILD before 'make docs'

sed -i 's,^#!/usr/bin/env python$,\02,' docs/bin/