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:
usbguard conflicts with itself

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

How reproducible:
simple

Steps to Reproduce:
1. install usbguard on RHEL 8.6
2. dnf check

Actual results:
usbguard-1.0.0-8.el8.ARCH has installed conflict "usbguard": usbguard-1.0.0-8.el8.ARCH

Expected results:
none

Additional info:
rpm -q usbguard --conflicts returns "usbguard"

I believe this was caused by a recent patch, bz#1963271.

Maybe zfridric can clarify it, as he was working on the usbguard component back then.

Hi,

I have a customer also hitting this on rhel 9. Since it looks like a spec file issue, I guess no workaround is available?. 

Any idea of a timeframe I could pass along to the cu?

-D

(In reply to Attila Lakatos from comment #1)
> I believe this was caused by a recent patch, bz#1963271.
> 
> Maybe zfridric can clarify it, as he was working on the usbguard component
> back then.

If I remember correctly, the issue that I was solving was that the system had older version of selinux-policy, therefore when you installed usbguard it installed older version of usbguard-selinux and older usbguard-selinux had older usbguard as a dependency, so it tried to install both usbguard and older usbguard and there was the conflict.

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 (usbguard 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/RHBA-2023:2833