Bug 11243 - ntp: FTBFS because of RPATH issues
Summary: ntp: FTBFS because of RPATH issues
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: ntp (show other bugs)
Version: 3
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Stefan Schantl
QA Contact:
URL:
Keywords: FTBFS
Depends on:
Blocks:
 
Reported: 2016-10-21 11:33 UTC by Michael Tremer
Modified: 2017-01-12 14:21 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tremer 2016-10-21 11:33:11 UTC
+ /usr/lib/pakfire/quality-agent
 W |   Has no canary: /builddir/ntp-4.2.8-2.ip3//usr/sbin/tickadj
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/sntp - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/tickadj - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntptime - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntp-keygen - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntpq - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntpdc - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntpdate - /usr/lib64
 E |   File has unallowed rpath: /builddir/ntp-4.2.8-2.ip3//usr/sbin/ntpd - /usr/lib64

I think I can reproduce this on all architectures, but at least on the 64bit ones.
Comment 1 Stefan Schantl 2016-10-21 13:12:51 UTC
Fix has been sent to the development mailing list.

http://patchwork.ipfire.org/patch/870/
Comment 2 Pakfire Build Service 2017-01-12 11:46:19 UTC
ntp-4.2.8-4.ip3 has been pushed to the IPFire 3 testing repository.

You can provide feedback for this build here:
  https://pakfire.ipfire.org/build/fe775674-3ceb-4b94-a535-43fa547b2dd4
Comment 3 Pakfire Build Service 2017-01-12 14:21:31 UTC
ntp-4.2.8-4.ip3 has been pushed to the IPFire 3 stable repository.

If problems still persist, please make note of it in this bug report.