# New builds in Arch Linux AUR **URL:** \ **Category:** Project Discussions\ **Tags:** ansible-navigator, distro-packaging\ **Created:** [June 1, 2025, 2:40am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091 "2025-06-01T02:40:00Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Alexander\_Jacocks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alexander_jacocks/32/8117_2.png) [@Alexander\_Jacocks](https://forum.ansible.com/u/Alexander_Jacocks)\ **Post date:** [June 1, 2025, 2:40am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/1 "2025-06-01T02:40:00Z")
I just updated the versions of the following packages, in the Arch AUR: [AUR (en) - ansible-creator](https://aur.archlinux.org/packages/ansible-creator) 25.5.0-1 [AUR (en) - ansible-navigator](https://aur.archlinux.org/packages/ansible-navigator) 25.5.0-1 [AUR (en) - ansible-dev-environment](https://aur.archlinux.org/packages/ansible-dev-environment) 25.5.0-1 If anyone has suggestions for improvement of the packages, please let me know. - Alex ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [June 1, 2025, 10:19am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/2 "2025-06-01T10:19:57Z")
Hi Alex, Thanks for updating those packages in the AUR! Your PKGBUILDs look generally good, although there are a few minor improvements that could be made according to the Arch packaging standards: - There’s no need for a package to provide and conflict itself, as this is [already done implicitly / automatically](https://wiki.archlinux.org/title/PKGBUILD#provides) (e.g. having `ansible-creator` [providing](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ansible-creator#n15) and [conflicting](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ansible-creator#n16) itself is not necessary and should be dropped) - We (Arch Linux) decided to stop relying on PyPI source tarballs for our python packages (when possible), you can read the rationales from the [related RFC](https://rfc.archlinux.page/0020-sources-for-python-packaging/). We now advise our package maintainers to rely upon sources directly from the upstream projects instead. For instance, relying on [GitHub’s auto-generated source tarball](https://github.com/ansible/ansible-creator/archive/refs/tags/v25.5.0.tar.gz) would be a good choice here regarding our guidelines. - There’s no need to `cd` to `$srcdir` in the different functions (`prepare()`, `build()`, `check()`, `package()`) as they are already executed from there. - The `ln -sf` dance in `build()` is pretty unusual and futile. You could simply `cd "${_pkgname}-${pkgver}"` directly in such case. - You defined `python-pytest` as a check dependency but the PKGBUILD doesn’t run tests. You should either introduce a [`check()` function](https://wiki.archlinux.org/title/Creating_packages#check()) to run said tests or, alternatively, drop the `checkdepends` array to avoid installing unused dependencies during the building process. - There’s no need to install the `Apache-2.0` license under `/usr/share/licenses/${pkgname}` as this license is already provided by our “generic” [licenses package](https://archlinux.org/packages/core/any/licenses/) (which is part of every Arch installation). See [this Wiki chapter](https://wiki.archlinux.org/title/PKGBUILD#license) for more details. - This is a minor detail, but your PKGBUILDs lack some “style” consistency _(e.g. sometimes arrays are quoted, sometimes not; variables are sometimes quoted, sometimes not; variables are sometimes in the form of `$var`, sometimes in the form of `${var}`)_. While we do not suggest one style over another, I personally prefer using the same one consistently over the whole PKGBUILD. Here is my personal “refinement” suggestion for the `ansible-creator` PKGBUILD, according to the above points (same could be applied to `ansible-navigator` and `ansible-dev-environment`): _successfully tested / built in a clean chroot_ ```auto # Maintainer: Alexander Jacocks pkgname=ansible-creator pkgver=25.5.0 pkgrel=1 pkgdesc="A CLI tool for scaffolding all your Ansible Content." arch=('any') url="https://github.com/ansible/ansible-creator" license=('Apache-2.0') depends=('python' 'python-jsonschema' 'python-onigurumacffi' 'ansible-core' 'ansible-runner' 'podman') makedepends=('python-build' 'python-installer' 'python-pip' 'python-setuptools' 'python-setuptools-scm' 'python-wheel') optdepends=('ansible: check official ansible collections') source=("${pkgname}-${pkgver}.tar.gz::${url}/archive/refs/tags/v${pkgver}.tar.gz") sha256sums=('f2cbd89021611463e26884ea179dd62c7a0e02c224e0fd21c38e8405be6f1506') build() { cd "${pkgname}-${pkgver}" export SETUPTOOLS_SCM_PRETEND_VERSION="${pkgver}" python -m build --wheel --no-isolation } package() { cd "${pkgname}-${pkgver}" python -m installer --destdir="${pkgdir}" dist/*.whl } ``` Again, your PKGBUILDs look good overall and my suggestions are _mostly_ about minor improvements. I hope that helps! 🙂 ---
**Author:** ![Alexander\_Jacocks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alexander_jacocks/32/8117_2.png) [@Alexander\_Jacocks](https://forum.ansible.com/u/Alexander_Jacocks)\ **Post date:** [June 1, 2025, 6:00pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/3 "2025-06-01T18:00:03Z")
Thanks so much Antiz! I’ll work on updating the packages with your suggestions. - Alex ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [June 19, 2025, 6:18am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/4 "2025-06-19T06:18:25Z")
Hi Alexander, Allow me to contact you through this thread to inform that I will have to move [the ansible-navigator AUR package](https://aur.archlinux.org/packages/ansible-navigator) to the official Arch Linux repository as a [new dependency](https://github.com/ansible/molecule/pull/4457) for our [molecule package](https://archlinux.org/packages/extra/any/molecule/). Given that the [ansible-navigator AUR repo](https://aur.archlinux.org/cgit/aur.git/tree/?h=ansible-navigator) currently does not include a LICENSE file, it would be welcome if you could add a [0BSD license](https://opensource.org/license/0bsd) to it. Without a 0BSD license, this package is not eligible for promotion to the official repositories _(or rather, not as-is)_. See the last bullet point in [the related Arch wiki section](https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission) and [the related RFC](https://rfc.archlinux.page/0040-license-package-sources/) for more details. Just to make things clean, this 0BSD license is only about package sources / build scripts (namely, in that case, the PKGBUILD itself); it is **not** about the distributed ansible-navigator software. I remain available if needed 🙂 Thanks in advance! ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [June 25, 2025, 7:19pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/5 "2025-06-25T19:19:00Z")
Hi @Alexander_Jacocks, Allow me a friendly ping, have you had the chance to see my above post? 🙂 ---
**Author:** ![Alexander\_Jacocks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alexander_jacocks/32/8117_2.png) [@Alexander\_Jacocks](https://forum.ansible.com/u/Alexander_Jacocks)\ **Post date:** [June 26, 2025, 2:58am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/6 "2025-06-26T02:58:45Z")
Antiz, I just saw this post. I’m glad to hear that you’ll be moving the package. I’ve added the license. What’s the process for the move? - Alex ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [June 26, 2025, 9:50am UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/7 "2025-06-26T09:50:20Z")
@Alexander_Jacocks Thanks for adding the license! I will handle the process for the move myself in a few, but here are the details: - I will create an `ansible-navigator` package in our official [extra] repository. The `pkgrel` of said package will be bumped (as compared to the AUR one) to ensure a smooth transition from the AUR package to the [extra] package for users - I will therefore become the package maintainer for the ansible-navigator package in our repository. Thanks to the 0BSD license you pushed, you will be listed as a (past) contributor for it (thanks 🤗) - I will then start a deletion process of the ansible-navigator AUR package, as it will then be considered a duplicate of the ansible-navigator package from our official repository. The ansible-navigator-git package you maintain in the AUR can remain however, no problem here 🙂 Let me know if you have further questions! ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [June 26, 2025, 1:09pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/8 "2025-06-26T13:09:34Z")
@Alexander_Jacocks ansible-navigator is now available in the official [Arch Linux [extra] repository](https://archlinux.org/packages/extra/any/ansible-navigator/) and has been deleted from the AUR. Thanks once again for your actions! You are obviously still free to open issues and merge request for the package in [its dedicated GitLab repository](https://gitlab.archlinux.org/archlinux/packaging/packages/ansible-navigator). For what it’s worth, I also moved [ansible-runner](https://archlinux.org/packages/extra/any/ansible-runner/) to the official repository as a dependency of `ansible-navigator`. ---
**Author:** ![Alexander\_Jacocks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alexander_jacocks/32/8117_2.png) [@Alexander\_Jacocks](https://forum.ansible.com/u/Alexander_Jacocks)\ **Post date:** [July 1, 2025, 4:03pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/10 "2025-07-01T16:03:10Z")
> [@Antiz](#): > > @Alexander_Jacocks ansible-navigator is now available in the official [Arch Linux [extra] repository](https://archlinux.org/packages/extra/any/ansible-navigator/) and has been deleted from the AUR. Sounds good, @Antiz. Glad to see more folks getting access to them. ---
**Author:** ![Antiz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/antiz/32/831_2.png) [@Antiz](https://forum.ansible.com/u/Antiz)\ **Post date:** [July 29, 2025, 10:46pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/11 "2025-07-29T22:46:51Z")
For information, I also moved `ansible-creator` to the official Arch Linux repo as a new (check) dependency of `ansible-lint`. ---
**Author:** ![Alexander\_Jacocks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alexander_jacocks/32/8117_2.png) [@Alexander\_Jacocks](https://forum.ansible.com/u/Alexander_Jacocks)\ **Post date:** [August 18, 2025, 2:15pm UTC](https://forum.ansible.com/t/new-builds-in-arch-linux-aur/43091/12 "2025-08-18T14:15:03Z")
Sounds good, I noticed. I just made changes to the ansible-dev-environment build and bumped the version.