Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#72621 - [molecule] should depend on ansible-core instead of ansible

Attached to Project: Community Packages
Opened by Amin Vakil (aminvakil) - Wednesday, 03 November 2021, 07:17 GMT
Last edited by David Runge (dvzrv) - Monday, 07 February 2022, 11:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Many roles and playbooks do not use modules which are in `ansible` package and depend solely on `ansible-core`, I guess it's best to keep the dependencies minimum and use `ansible-core` for `molecule` dependencies.

Additional info:
molecule 3.5.2-1

In fact `molecule` does not even need `ansible-core` as states and `ansible-core` (`ansible-base` 2.10) and `ansible` are both in optional dependencies.

It uses some new package called `ansible-compat`, but I don't know exactly what it does, for now I guess it's best to change the `ansible` dependency to `ansible-core`.

This task depends upon

Closed by  David Runge (dvzrv)
Monday, 07 February 2022, 11:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with 3.6.0-1