RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

In repo config files in /etc/yum.repos.d one can set a "priority" value for a repository. If the priority level for a repo is set higher than for other repos, packages from that repo will not displace packages from other repos even when the package version is higher.

It appears that gnome-software does NOT respect this setting for its "updates" list.

Version-Release number of selected component (if applicable):

3.30.6

How reproducible:

Appears to reproduce every time

Steps to Reproduce:
1. Install the epel-release package.
2. Enable the epel-playground repo. Set its priority to 255.
3. Open gnome-software and select Updates.

Actual results:

The updates include changes from epel-playground.

Expected results:

No updates from epel-playground.

Additional info:

The code that should handle the "priority" setting is all in libdnf. Reassigning.

PR https://github.com/rpm-software-management/libdnf/pull/961

Added a test to my PR with other repo config options problems: https://github.com/rpm-software-management/ci-dnf-stack/pull/831

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (yum bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4510