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.

# Steps to reproduce:

```
sudo yum install -y brltty-5.6-32.el8.i686 brltty-5.6-32.el8.x86_64
```

## Expected behavior

1. Everything install

## Current behavior:

Total                                                                                                       5.3 MB/s |  12 MB     00:02     
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: Transaction test error:
  file /etc/brltty.conf conflicts between attempted installs of brltty-5.6-32.el8.i686 and brltty-5.6-32.el8.x86_64
  file /usr/bin/brltty-config conflicts between attempted installs of brltty-5.6-32.el8.i686 and brltty-5.6-32.el8.x86_64
  file /usr/share/man/man1/brltty.1.gz conflicts between attempted installs of brltty-5.6-32.el8.i686 and brltty-5.6-32.el8.x86_64

brltty is not library, so it shouldn't be multilib. I think the 32 bit version was wrongly put to the repo because there was badly defined dependencies in the brltty spec. This is now fixed. The conflict itself is not easy to solve. Even if we solve it, it will result in installation of the 32 bit drivers which without the 32 bit brltty binary (which will be not installed due to the coloring) are probably useless. I think if the brltty.i686 was introduced to the repo, we shouldn't drop it (it can be still used if the 64 bit version is not installed). That's why I recommend just documenting this problem as a known issue.

Possible fix (which I do not recommend):
- drop the drivers-directory option and its description from the /etc/brltty.conf, rely on the built-in defaults
- add wrapper for the brltty-config with some bash magic for detection of the 32/64 bit
- drop the 32/64 bit parts from the manual page (brltty.1.gz)

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.