Bug 1144863

Summary: chrpath Missing biarch/multiarch/multilib support ; new upstream release
Product: [Fedora] Fedora Reporter: Hin-Tak Leung <htl10>
Component: chrpathAssignee: David King <amigadave>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: Axel.Thimm
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: chrpath-0.16-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-18 10:36:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hin-Tak Leung 2014-09-21 16:26:12 UTC
Description of problem:
Trying to grab the llvm source rpm from koji and build 32-bit version of llvm on fc20 x86_64 (to get 32-bit mesa Gallium drm driver...) and encounted some problems which I'll report to llvm directly; but the last remaining problem is in the rpm spec file which uses chrpath - it does this:

--------------
# remove RPATHs
file %{buildroot}/%{_bindir}/* | awk -F: '$2~/ELF/{print $1}' | xargs -r chrpath -d
file %{buildroot}/%{_libdir}/llvm/*.so | awk -F: '$2~/ELF/{print $1}' | xargs -r chrpath -d
--------------

0.13 doesn't support multi-arch fully. This is fixed from 0.14 onwards.

Version-Release number of selected component (if applicable):
chrpath-0.13-13.fc20.x86_64


How reproducible:
Always.

Steps to Reproduce:
1. Just watch chrpath "any 32-bit binary" on a x86_64.
2.
3.

Actual results:
'any 32-bit binary' probably isn't a 64-bit LSB-first ELF file.
elf_open: Exec format error

Expected results:
exit silently/successfully.

Additional info:
See also the Bebian bug report;
upstream seems to have moved or forked to

https://alioth.debian.org/projects/chrpath/ , https://chrpath.alioth.debian.org/ 

 and there is a release 0.16 .
https://alioth.debian.org/frs/download.php/file/3979/chrpath-0.16.tar.gz released on 2014-01-14  .

Comment 1 Fedora Admin XMLRPC Client 2015-02-25 19:56:35 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Update System 2015-02-25 21:16:39 UTC
chrpath-0.16-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/chrpath-0.16-1.fc22

Comment 3 Hin-Tak Leung 2015-02-25 21:51:20 UTC
Left comment in the admin page. It works on f21 now:

 chrpath /usr/lib/libGL.so.1
/usr/lib/libGL.so.1: no rpath or runpath tag found.

Comment 4 Fedora Update System 2015-03-04 09:14:21 UTC
chrpath-0.16-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/chrpath-0.16-1.fc20

Comment 5 Fedora Update System 2015-03-07 21:52:13 UTC
chrpath-0.16-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/chrpath-0.16-1.fc21

Comment 6 Fedora Update System 2015-03-09 08:37:12 UTC
chrpath-0.16-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-03-09 08:40:28 UTC
Package chrpath-0.16-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing chrpath-0.16-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3530/chrpath-0.16-1.fc21
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-03-18 10:36:46 UTC
chrpath-0.16-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-03-21 05:01:35 UTC
chrpath-0.16-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.