After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697840 - tracker uses incorrect libtool
tracker uses incorrect libtool
Status: RESOLVED NOTGNOME
Product: tracker
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Depends on:
Blocks:
 
 
Reported: 2013-04-11 23:16 UTC by Rafał Mużyło
Modified: 2013-04-23 19:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rafał Mużyło 2013-04-11 23:16:37 UTC
This regards a series of problems described at https://bugs.gentoo.org/show_bug.cgi?id=367975.

It's about tracker linking to its libs already on the system, instead the ones it builds.

It can be noticed with ie. 0.12 -> 0.14 upgrade, but also with icu 49 -> 51 upgrade.

It's caused by minor mistake, that is the use of something called '(GNU libtool) 2.4.2 Debian-2.4.2-ubuntu2'. If that mistake is corrected, that is vanilla libtol 2.4.2 is used, tracker builds correctly.
Comment 1 Martyn Russell 2013-04-12 08:40:49 UTC
Hello Rafal, so just to understand what you're saying, it looks like if we make dist (for the tarball) with the right libtool, this bug is fixed?
Comment 2 Rafał Mużyło 2013-04-12 17:53:46 UTC
(In reply to comment #1)
> Hello Rafal, so just to understand what you're saying, it looks like if we make
> dist (for the tarball) with the right libtool, this bug is fixed?

Right, it's not like you keep those files in the repo, it's just the matter of whoever generates those tarballs (it's more of a bug of the Debian/Ubuntu patch, than tracker, but as the tarballs have been generated with it in quite awhile and I don't use Debian, it's not really something *I* should report there).
Comment 3 Martyn Russell 2013-04-23 15:29:44 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Hello Rafal, so just to understand what you're saying, it looks like if we make
> > dist (for the tarball) with the right libtool, this bug is fixed?
> 
> Right, it's not like you keep those files in the repo, it's just the matter of
> whoever generates those tarballs (it's more of a bug of the Debian/Ubuntu
> patch, than tracker, but as the tarballs have been generated with it in quite
> awhile and I don't use Debian, it's not really something *I* should report
> there).

Thank you for reporting the bug Rafał. I am going to mark this as NOTGNOME though. The reason being, I have to create the tarballs from some distribution and i'm not changing my distro to fix the libtool issue :)

You can certainly check out the code form the git repository and create the tarball yourself with make dist.

Any problems, let me know.
Comment 4 Pacho Ramos 2013-04-23 17:03:10 UTC
Doesn't look correct to me to generate tarballs with unofficial tools that leads to problems in distributions using more similar to upstream ones. This problem should at least be reported to ubuntu people to try to fix this problem in their libtool
Comment 5 Martyn Russell 2013-04-23 19:20:52 UTC
(In reply to comment #4)
> Doesn't look correct to me to generate tarballs with unofficial tools that
> leads to problems in distributions using more similar to upstream ones. This
> problem should at least be reported to ubuntu people to try to fix this problem
> in their libtool

I agree about reporting it to Canonical/Ubuntu.

Also, nothing stops people from creating their own tarball from the tagged version in the git repository. That solves the problem for anyone that has it.