You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The module expects the default output from pacman and cannot currently cope with the verbose output.
Since it is not possible to turn off the verbose output from pacman's cli, I ended up adding a simple wrapper script that uses pacman-conf to grep out the verbose output option and using that as pacman's executable:
I feel like the pacman module should work regardless of what display options are used in the system config file, but at the same time I'm not sure how to fix this properly.
Relying on the human readable output of the tool feels brittle and adding a new parser for the verbose output wouldn't help in the long run if that format ever changes.
I kinda wish pacman could output in a stable format, like json or something like that.
In any case, maybe the above will help other people who like the Verbose format :-)
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Summary
If
VerbosePkgLists
is present inpacman.conf
, the diff output generated by the pacman plugin is broken:Issue Type
Bug Report
Component Name
pacman
Ansible Version
Community.general Version
Configuration
$ ansible-config dump --only-changed
OS / Environment
Arch
Steps to Reproduce
Add
VerbosePkgLists
to/etc/pacman.conf
and run a task that installs a pkg viapacman
.Expected Results
Actual Results
The module expects the default output from
pacman
and cannot currently cope with the verbose output.Since it is not possible to turn off the verbose output from pacman's cli, I ended up adding a simple wrapper script that uses
pacman-conf
to grep out the verbose output option and using that as pacman's executable:I feel like the pacman module should work regardless of what display options are used in the system config file, but at the same time I'm not sure how to fix this properly.
Relying on the human readable output of the tool feels brittle and adding a new parser for the verbose output wouldn't help in the long run if that format ever changes.
I kinda wish
pacman
could output in a stable format, like json or something like that.In any case, maybe the above will help other people who like the Verbose format :-)
Code of Conduct
The text was updated successfully, but these errors were encountered: