Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Why does this happen and how can it be fixed?
file /usr/lib/.build-id/02/f209a47a21452e7e4131c9e0b78af2f17e2d1e from install of rstudio-1.2.5033-1.x86_64 conflicts with file from package nsight-compute-2019.4.0-2019.4.0.12-1.x86_64
Note also seen on Fedora: https://community.rstudio.com/t/fedora-29-install-rstudio-desktop-failed/46996/4
The packages a file with an identical build-id in two different locations. This is generally supposed to be a can't happen situation and a likely cause is packaging a binary file copied from some other package, but could in theory also be an identical file compiled in identical conditions to a different name.
As both packages here are something of a proprietary nature, I suspect its binaries copied from someplace else to avoid dependency problems, but such copying can also be subject to licensing issues (way out of scope here).
These need to be reported to the packagers of said software to sort out one way or the other. One possibility is moving the build-id links to debuginfo packages with eg this in the spec:
%global _build_id_links alldebug
To workaround, install with rpm using "--excludepath=/usr/lib/.build-id/" is probably the cleanest workaround (--force will also do the trick, just with a bigger hammer)