Hi,
On the 3rd May I built libxfce4util and generated
libxfce4util2_4.3.90.1-1_amd64.deb. This is in the archive exactly as I
built it. It has a couple of lintian failures that I missed and have since
been fixed in our SVN.
Upstream have released recently and whilst checking these packages more
thoroughly I've fixed up the lintian errors but I've also built the new
package and I noticed that it's defining an rpath. So I rooted around and
tried to work out why but couldn't really work it out. Upstream's
libtool and autotools looked recent to me. If I relibtoolize though
this does go away.
Out of curiousity I rebuilt the previous package i.e. 4.3.90.1-1 again from
the same source files as before but with current sid and this time it fails
with two extra lintian warnings:
W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/lib/libxfce4util.so.2.1.0 /usr/lib
W: libxfce4util2: binary-or-shlib-defines-rpath ./usr/sbin/xfce4-kiosk-query /usr/lib
If I rebuild the same package on i386 current sid then I don't get the rpath
installed.
I guess I have several questions:
- how can the same source package over a few months build
differently in this way?
- am I really going to have to relibtoolize every xfce package
before I upload or make them do it themselves? :-/
- how evil is an rpath on /usr/lib anyway?
I'd welcome any testers on amd64 or not and on recent sid or not to narrow
this down. Or any clues as to how on earth this can happen.
If you do want to relibtoolize then install xfce4-dev-ools and run
xdt-autogen in the package dirrectory.
Thanks.
Simon.
heh, good sigmonster.
--
oOoOo Open source is about letting go of complete control. Accept oOoOo
oOoOo the fact that other people are wonderful resources to oOoOo
oOoOo fixing problems, and let them help you. - Linus Torvalds oOoOo
htag.pl 0.0.22 ::::::: http://www.earth.li/~huggie/
Attachment:
signature.asc
Description: Digital signature