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 repo-packages: key in a treefile always fails to find the listed packages if the repo: is set to the name of an enabled non-local repo provided in the *.repo file.
Reproduction steps
Create an HTTPS-enabled RPM repo on some system
Add a unique RPM to it and ensrue the metadata is up to date
Create a *.repo file pointing to that RPM repo
Create a treefile that lists that repo, and lists the unique RPM under the packages key
Verify the rpm-ostree compose tree --downloadonly works properly, including that unique package
Modify the treefiles to put the unique RPM under a repo-packages key. Example:
repos:
- my-custom-repo
- fedora
- updatespackages:
# ...snip...## this works when enabled instead of the repo-packages#- my-unique-rpmrepo-packages:
- repo: my-custom-repopackages:
- my-unique-rpm
Run a clean build
Expected behavior
The RPM (my-unique-rpm) is found from the my-custom-repo RPM repo the same as when it was successfully used by the packages: key.
Actual behavior
error: Installing packages: No matches for 'my-unique-rpm' in repo 'my-custom-repo'
System details
Using the latest coreos-assembler container image as of today.
From searching the GitHub Issues, it looks like RHEL and some others might be successfully using the repo-packages: to pull from a local RPM repo. I don't have a good way to test or verify whether that works, but I do have a pre-existing RPM repo that works with DNF, and works as part of the repo: key in a treefile to successfully select packages using the packages: key that only exist in that one repo (private RPMs not available anywhere else).
The text was updated successfully, but these errors were encountered:
Describe the bug
The
repo-packages:
key in a treefile always fails to find the listed packages if therepo:
is set to the name of an enabled non-local repo provided in the *.repo file.Reproduction steps
packages
keyrpm-ostree compose tree --downloadonly
works properly, including that unique packagerepo-packages
key. Example:Expected behavior
The RPM (
my-unique-rpm
) is found from themy-custom-repo
RPM repo the same as when it was successfully used by thepackages:
key.Actual behavior
System details
rpm-ostree --version
:Additional information
From searching the GitHub Issues, it looks like RHEL and some others might be successfully using the
repo-packages:
to pull from a local RPM repo. I don't have a good way to test or verify whether that works, but I do have a pre-existing RPM repo that works with DNF, and works as part of therepo:
key in a treefile to successfully select packages using thepackages:
key that only exist in that one repo (private RPMs not available anywhere else).The text was updated successfully, but these errors were encountered: