Small grammatical corrections: # ansible-core >= 2.15.3-1 update may require manual intervention As of ansible-core version `2.15.3`, upstream moved documentation and examples to a separate [dedicated repository](https://github.com/ansible/ansible-documentation) (see the [related changelogs](https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHANGELOG-v2.15.r...)). This means that, starting from version `2.15.3` the `ansible-core` package will stop shipping documentation and a default configuration example under `/etc/ansible/ansible.cfg`. Regarding the documentation, it is available online: https://docs.ansible.com/ As for the configuration file, as explained in the [wiki](https://wiki.archlinux.org/title/Ansible#Configuration), a base config can be generated with the following command: ```sh ansible-config init --disabled > ansible.cfg ``` After updating from ansible-core <= `2.15.2-1` to >= `2.15.3-1`, everyone using a **custom** global Ansible configuration file stored under `/etc/ansible/ansible.cfg` will have their configuration saved as a `pacsave` file. To restore it, run the following command: ```sh mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg ``` Le 17/08/2023 à 17:53, Robin Candau a écrit :

Le 17/08/2023 à 17:47, Robin Candau a écrit :

...

# ansible-core >= 2.15.3-1 update may require manual intervention

As of ansible-core version `2.15.3`, upstream moved documentations and examples to a separated [dedicated repository](https://github.com/ansible/ansible-documentation) (see the [related changelogs](https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHANGELOG-v2.15.r...)).

This means that, starting from version `2.15.3` the `ansible-core` package will stop shipping documentations and a default configuration example under `/etc/ansible/ansible.cfg`.

Regarding the documentation, it is available online: https://docs.ansible.com/ As for the configuration file, as explained in the [wiki](https://wiki.archlinux.org/title/Ansible#Configuration), a base config can be generated with the following command:

```sh ansible-config init --disabled > ansible.cfg ```

After updating from ansible-core <= `2.15.2-1` to >= `2.15.3-1`, everyone using a global Ansible configuration file stored under everyone using a **custom** global Ansible configuration file [...] `/etc/ansible/ansible.cfg` will have their configuration saved as a `pacsave` file. To re-instore it, run the following command:

```sh mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg ```

-- Regards, Robin Candau / Antiz