Bug 736739

Summary: usbutils update moves lsusb from /usr/sbin to /usr/bin
Product: Red Hat Enterprise Linux 6 Reporter: Bryn M. Reeves <bmr>
Component: usbutilsAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: dfediuck, dkutalek, isenfeld, jwest, ovasik, syeghiay
Target Milestone: betaKeywords: Regression
Target Release: 6.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: usbutils-003-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 807263 (view as bug list) Environment:
Last Closed: 2011-12-06 16:18:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 691477, 743047, 807263    

Description Bryn M. Reeves 2011-09-08 15:01:05 UTC
Description of problem:
usbutils-003-2.el6 moves the lsusb binary from /usr/sbin to /usr/bin:

# rpm -qlp usbutils-0.86-2.el6.x86_64.rpm | grep bin
/usr/bin/usb-devices
/usr/sbin/lsusb

# rpm -qlp usbutils-003-2.el6.x86_64.rpm | grep bin
/usr/bin/lsusb
/usr/bin/lsusb.py
/usr/bin/usb-devices
/usr/bin/usbhid-dump

This breaks distribution & third party scripts that rely on the old location.

Version-Release number of selected component (if applicable):
usbutils-003-2.el6

How reproducible:
100%

Steps to Reproduce:
1. $ /usr/sbin/lsusb

Actual results:
-bash: /usr/sbin/lsusb: No such file or directory

Expected results:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[...]

Additional info:
A symlink to the old location would retain compatibility with the path used in previous RHEL6 updates.

Comment 6 errata-xmlrpc 2011-12-06 16:18:39 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1646.html