ArchPOWER/packages
1
0
Fork 0
Code Issues 8 Pull Requests 1 Actions Packages Projects Releases 18 Wiki Activity

* update ansible to 11.1.0-2

Browse Source
This commit is contained in:
Alexander Baldeck 2025-01-07 17:23:20 +01:00
parent 124fd9d39b
commit f1e7fe8236
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
python/ansible/.SRCINFO
View File

@ -1,6 +1,6 @@
pkgbase = ansible
pkgdesc = Official assortment of Ansible collections
pkgver = 11.0.0
pkgver = 11.1.0
pkgrel = 2
url = https://pypi.org/project/ansible/
arch = any
@ -17,7 +17,7 @@ pkgbase = ansible
optdepends = python-ovirt-engine-sdk: ovirt support
optdepends = python-boto3: aws_s3 module
optdepends = python-ldap: ldap support
optdepends = python-proxmoxer: proxmos modules
optdepends = python-proxmoxer: proxmox modules
optdepends = python-openstacksdk: OpenStack module
optdepends = python-pynetbox: NetBox module
optdepends = python-ldap: LDAP modules
@ -27,7 +27,7 @@ pkgbase = ansible
optdepends = python-lxc: LXC module
optdepends = acme-tiny: openssl_certificate module
provides = python-ansible_collections
source = https://pypi.python.org/packages/source/a/ansible/ansible-11.0.0.tar.gz
sha512sums = 9687703af0f4093ba4dadb530d9a257fac038a09ed6fead430247198b9f03257790602194fd01ba74db1ba20695fb2d6a37836602e6721a8c42e69e27314f3c1
source = https://pypi.python.org/packages/source/a/ansible/ansible-11.1.0.tar.gz
sha512sums = d78f7c6f7a0a1563b270408268dc84dc1796fe7ec8355da3eb9489ffda44328a9836b05d3067516452790fe1cdf2c2ad67b285a5a97444d6403aaf79491d42c0
pkgname = ansible

6
python/ansible/PKGBUILD
View File

@ -3,7 +3,7 @@
# Maintainer: Robin Candau <antiz@archlinux.org>
pkgname=ansible
pkgver=11.0.0
pkgver=11.1.0
pkgrel=2
pkgdesc='Official assortment of Ansible collections'
arch=(any)
@ -17,7 +17,7 @@ optdepends=('python-argcomplete: shell completions'
'python-ovirt-engine-sdk: ovirt support'
'python-boto3: aws_s3 module'
'python-ldap: ldap support'
'python-proxmoxer: proxmos modules'
'python-proxmoxer: proxmox modules'
'python-openstacksdk: OpenStack module'
'python-pynetbox: NetBox module'
'python-ldap: LDAP modules'
@ -28,7 +28,7 @@ optdepends=('python-argcomplete: shell completions'
'acme-tiny: openssl_certificate module')
makedepends=('python-build' 'python-installer' 'python-wheel' 'python-setuptools')
source=("https://pypi.python.org/packages/source/a/ansible/ansible-${pkgver}.tar.gz")
sha512sums=('9687703af0f4093ba4dadb530d9a257fac038a09ed6fead430247198b9f03257790602194fd01ba74db1ba20695fb2d6a37836602e6721a8c42e69e27314f3c1')
sha512sums=('d78f7c6f7a0a1563b270408268dc84dc1796fe7ec8355da3eb9489ffda44328a9836b05d3067516452790fe1cdf2c2ad67b285a5a97444d6403aaf79491d42c0')
build() {
cd "ansible-${pkgver}"

2
python/ansible/README.md
View File

@ -10,4 +10,4 @@ To put it simply, `ansible` new releases should always be built against an up to
Fortunately, upstream usually syncs the releases of new `ansible` and `ansible-core` versions. They are usually released a few hours apart (with `ansible-core` always being released first).
As a matter of precaution, it is appropriate to maintain both `ansible` and `ansible-core` as one package group (e.g. package, release and move new versions accross repositories at the same time).
As a matter of precaution, it is appropriate to maintain both `ansible` and `ansible-core` as one package group (e.g. package, release and move new versions of those packages accross repositories together).