mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-06-30 12:10:22 -07:00
[PR #10238/19568158 backport][stable-10] docs: add notes that dnf_* modules do not work with dnf5 (#10247)
docs: add notes that dnf_* modules do not work with dnf5 (#10238)
* Add notes that dnf_* modules do not work with dnf5.
* Apply suggestions from code review.
---------
(cherry picked from commit 1956815884
)
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com>
This commit is contained in:
parent
cae0457e0e
commit
9c3e14701b
2 changed files with 3 additions and 0 deletions
|
@ -39,6 +39,8 @@ options:
|
||||||
required: false
|
required: false
|
||||||
type: str
|
type: str
|
||||||
choices: [enabled, disabled]
|
choices: [enabled, disabled]
|
||||||
|
notes:
|
||||||
|
- Does not work with C(dnf5).
|
||||||
seealso:
|
seealso:
|
||||||
- module: ansible.builtin.dnf
|
- module: ansible.builtin.dnf
|
||||||
- module: ansible.builtin.yum_repository
|
- module: ansible.builtin.yum_repository
|
||||||
|
|
|
@ -60,6 +60,7 @@ notes:
|
||||||
- In an ideal world, the C(versionlock) plugin would have a dry-run option to know for sure what is going to happen. So
|
- In an ideal world, the C(versionlock) plugin would have a dry-run option to know for sure what is going to happen. So
|
||||||
far we have to work with a best guess as close as possible to the behaviour inferred from its code.
|
far we have to work with a best guess as close as possible to the behaviour inferred from its code.
|
||||||
- For most of cases where you want to lock and unlock specific versions of a package, this works fairly well.
|
- For most of cases where you want to lock and unlock specific versions of a package, this works fairly well.
|
||||||
|
- Does not work with C(dnf5).
|
||||||
requirements:
|
requirements:
|
||||||
- dnf
|
- dnf
|
||||||
- dnf-plugin-versionlock
|
- dnf-plugin-versionlock
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue