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:
 file /usr/share/glib-2.0/schemas/org.gnome.gedit.enums.xml conflicts between attempted installs of gedit-2:3.22.0-3.el7.i686 and gedit-2:3.22.0-3.el7.x86_64

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


How reproducible:
gedit-2:3.22.0-3.el

Steps to Reproduce:
1.
2.
3.

Actual results:
file /usr/share/glib-2.0/schemas/org.gnome.gedit.enums.xml conflicts between attempted installs of gedit-2:3.22.0-3.el7.i686 and gedit-2:3.22.0-3.el7.x86_64

Expected results:
should not conflict

Additional info:

i'm confused, why is gedit getting pulled in as a multilib package?  is some library doing Requires: gedit ?

(In reply to Ray Strode [halfline] from comment #1)
> i'm confused, why is gedit getting pulled in as a multilib package?  is some
> library doing Requires: gedit ?

Hope it is not, I bet it get pulled in with TPS lists.

But still someone could for whatever reason try to install both. So we can at least document.

well there's a ton of packages that we don't support installing both 32-bit and x86-64 at the same time with.  We don't document every case that doesn't work afaik.  It's never been something we've supported.  That's why we broke out a bunch of packages to have -libs subpackages, so the multilib conflicting parts would be segregated from the libraries (where multilib is usually more important).

(s/x86-64/64-bit/ above obviously)

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.