Hi Matías!

On Mon, 17 Aug 2026 15:52:33 -0300 =?utf-8?q?Mat=C3=ADas_Teplitzky?= <[email protected]> wrote:
Package: ansible
Version: 12.0.0+dfsg-0+deb13u1
Severity: wishlist
X-Debbugs-Cc: [email protected]

Dear Maintainer,

I think it would be useful for Debian users to have a README.Debian file that
explains how maintainers of the Ansible package expect the included Ansible
tooling to be used, when installed from the official Debian repositories. In
particular, I think such inclusion would be justified if it's taken into account
that (to the best of my knowledge) Ansible package in Debian:

1) It doesn't ship with a default global Ansible configuration file (e.g: 
/etc/ansible/ansible.cfg).
2) It doesn't ship with a default setting for the Ansible inventory file 
location.

The common choice is to provide ansible.cfg in the dir where your roles and playbooks already reside, the ansible binaries will automatically pick it up. inventory is set in ansible.cfg, or passed via -i from the command line and should also reside in that directory. The upstream tutorial uses the same approach:
https://docs.ansible.com/projects/ansible/latest/getting_started/get_started_inventory.html#get-started-inventory

AFAICS a pip install of ansible would also not ship a globale ansible config (/etc/ansible/ansible.cfg) and global inventory file (/etc/ansible/hosts), so we're not different to that.

I'd argue that neither ansible config nor inventory should be a global setting anyway, since they're closely related to the playbooks you have written. That's a bit of an unfortunate default by upstream, I'm guessing more for historical reasons. In a common scenario where you share the ansible repo with other peers (admin group), the playbooks won't work without the corresponding inventory, as such it should go in the same repo.

This bug is not aimed to criticize the way Ansible is packaged in Debian but
rather to simply ask for the inclusion of a text file with, may be, a quick
how-to on getting started using Ansible in Debian and some clarification on the
points mentioned above.

Fair point, and not offense taken. To be fair, I've been using ansible for so long that I don't notice speed bumps like that. With the knowledge from above, do you think it's still useful to ship something in README.Debian? If yes, would you like to draft it? I'd then review it and ship it in the next upload.


Thanks.
Cheers.

Best regards,
Lee


-- System Information:
Debian Release: 13.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.100+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ansible depends on:
ii  ansible-core       2.19.4-0+deb13u1
ii  openssh-client     1:10.0p1-7+deb13u4
ii  python3            3.13.5-1
ii  python3-dnspython  2.7.0-1
ii  python3-httplib2   0.22.0-1
ii  python3-jinja2     3.1.6-1
ii  python3-netaddr    1.3.0-1
ii  python3-yaml       6.0.2-1+b2

Versions of packages ansible recommends:
pn  python3-argcomplete   <none>
ii  python3-cryptography  43.0.0-3+deb13u1
pn  python3-jmespath      <none>
pn  python3-kerberos      <none>
pn  python3-libcloud      <none>
pn  python3-selinux       <none>
pn  python3-winrm         <none>
pn  python3-xmltodict     <none>

Versions of packages ansible suggests:
pn  cowsay   <none>
ii  sshpass  1.10-0.1


Reply via email to