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:
I believe libusbmuxd-utils subpackage should most probably obsolete usbmuxd.

Version-Release number of selected component (if applicable):
libusbmuxd-utils-1.0.10-5.el7
usbmuxd-1.0.8-12.el7

How reproducible:
100%

Steps to Reproduce:
1. install libusbmuxd when usbmuxd is already installed
2.
3.

Actual results:
file /usr/bin/iproxy from install of libusbmuxd-utils-1.0.10-5.el7.x86_64 conflicts with file from package usbmuxd-1.0.8-12.el7.x86_64


Expected results:
no sdterr output

Additional info:
I know this issue belongs more to libusbmuxd but this component is not yet in bugzilla so failing against usbmuxd for now until libusbmuxd get created.

Also libusbmuxd should provide smillas stuff as usbmuxd did, as it is required by some of gvfs rpms (I think it is gvfs-afc).

Looks like usbmuxd was split into two (usbmuxd+libusbmuxd), but we've only included one half of the split (libusbmuxd) for the rebase. We should get the other half of the split, usbmuxd updated as well.

In Fedora, usbmuxd commit http://pkgs.fedoraproject.org/cgit/rpms/usbmuxd.git/commit/?id=5c2aa1ae0ba2c1e3c627803f3c4b4950171cd49a dropped the conflicting files, we should do the same (but not update to the snapshot from 2014, but latest release of course).

Should be fixed in usbmuxd-1.1.0-1.el7

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, 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-2017:2137