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 packages key in a treefile supports listing whitespace-separated package names, package names that attempt to match the NEVRA follwing the dnf file name rules (e.g. kernel-6.9.11-0.fc39), or version query syntax (e.g. "'kernel = 6.9'").
The repo-packages[].packages however only supports names, and does not support either of the other syntax options. This means it's not possible to pin a package to a specific version from a specific repo, you can theoretically only pin a named package to a repo if you're willing to always take the latest version offered by that repo.
Reproduction steps
List a specific package version as part of the packages key in a working treefile. Example:
Describe the bug
The
packages
key in a treefile supports listing whitespace-separated package names, package names that attempt to match the NEVRA follwing thednf
file name rules (e.g.kernel-6.9.11-0.fc39
), or version query syntax (e.g."'kernel = 6.9'"
).The
repo-packages[].packages
however only supports names, and does not support either of the other syntax options. This means it's not possible to pin a package to a specific version from a specific repo, you can theoretically only pin a named package to a repo if you're willing to always take the latest version offered by that repo.Reproduction steps
packages
key in a working treefile. Example:repo-packages
section. Example:Expected behavior
The configuration works identically, only adding the assurance that the packages came from the specific repo.
Actual behavior
System details
rpm-ostree --version
Additional information
No response
The text was updated successfully, but these errors were encountered: