Bug 866513 - /sbin/parted & /sbin/partprobe depend on libs in /usr/
/sbin/parted & /sbin/partprobe depend on libs in /usr/
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: parted (Show other bugs)
5.9
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Brian Lane
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-15 10:29 EDT by Alexander Todorov
Modified: 2013-04-01 14:13 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-04-01 14:13:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2012-10-15 10:29:48 EDT
Description of problem:

:: [   FAIL   ] :: /sbin/parted (Assert: "0" should not equal "0")
:: [   LOG    ] :: 	libparted-1.8.so.0 => /usr/lib/libparted-1.8.so.0 (0x2000000800050000)
:: [   LOG    ] :: 	libreadline.so.5 => /usr/lib/libreadline.so.5 (0x200000080027c000)
:: [   LOG    ] :: 	libncurses.so.5 => /usr/lib/libncurses.so.5 (0x20000008002f8000)
:: [   FAIL   ] :: /sbin/partprobe (Assert: "0" should not equal "0")
:: [   LOG    ] :: 	libparted-1.8.so.0 => /usr/lib/libparted-1.8.so.0 (0x2000000800050000)
:: [   LOG    ] :: 	libreadline.so.5 => /usr/lib/libreadline.so.5 (0x200000080027c000)
:: [   LOG    ] :: 	libncurses.so.5 => /usr/lib/libncurses.so.5 (0x20000008002f8000)
Comment 1 Brian Lane 2012-10-15 11:21:23 EDT
I need some context here. What's generating these errors? And why is this a problem? Nothing in parted has changed in relation to library locations.
Comment 4 David Cantrell 2013-04-01 14:13:07 EDT
This is largely cosmetic, not really appropriate for .10 and later update releases.

The risk of regression from tools that expect /sbin/parted outweighs the benefit of moving parted and partprobe to /usr/sbin.

Note You need to log in before you can comment on or make changes to this bug.