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 762512 - Build fails with libcue 2.0
Build fails with libcue 2.0
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Extractor
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-extractor
tracker-extractor
Depends on:
Blocks:
 
 
Reported: 2016-02-23 07:50 UTC by Antonio Rojas
Modified: 2016-03-21 19:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to fix build against libcue 2.0 (981 bytes, patch)
2016-02-23 07:50 UTC, Antonio Rojas
none Details | Review
libcue 2.0 support (2.58 KB, patch)
2016-02-28 15:00 UTC, Marinus Schraal
none Details | Review
libcue 2.0 support (2.59 KB, patch)
2016-03-02 11:22 UTC, Marinus Schraal
committed Details | Review

Description Antonio Rojas 2016-02-23 07:50:26 UTC
Created attachment 321925 [details] [review]
patch to fix build against libcue 2.0

libcue 2.0 has been released with two changes that break tracker build
- the header file has been moved to the top-level include dir
- the Cmt enum has been renamed to RemType

The attached patch fixes the build against libcue 2.0, although it will need to be adapted to work with libcue 1.x too.
Comment 1 Marinus Schraal 2016-02-28 15:00:36 UTC
Created attachment 322585 [details] [review]
libcue 2.0 support

Updated the patch with conditional support for the 2.0 API changes & configure foo.

Tracker should work with the 2.0 version just fine, since the API change is just an enum rename.

See https://github.com/lipnitsk/libcue/releases for more info.
Comment 2 David King 2016-03-02 09:42:03 UTC
Review of attachment 322585 [details] [review]:

The PKG_CHECK_EXISTS change looks fine to me.

::: configure.ac
@@ +2407,2 @@
 AM_CONDITIONAL(HAVE_LIBCUE, test "x$have_libcue" = "xyes")
+AM_CONDITIONAL(HAVE_LIBCUE2, test "x$have_libcue2" = "xyes")

These automake conditionals are not used; is there any reason to keep them?
Comment 3 Marinus Schraal 2016-03-02 11:22:28 UTC
Created attachment 322841 [details] [review]
libcue 2.0 support

You are correct, the conditionals are redundant.
Comment 4 David King 2016-03-02 11:48:59 UTC
Review of attachment 322841 [details] [review]:

Looks good (and builds fine) to me. I'm not a tracker developer, so just marking this as "reviewed".
Comment 5 César Fabián Orccón Chipana 2016-03-19 15:15:29 UTC
Looks good to me, too.
Comment 6 César Fabián Orccón Chipana 2016-03-19 15:15:57 UTC
Review of attachment 322841 [details] [review]:

It should be merged upstream.
Comment 7 Carlos Garnacho 2016-03-21 19:40:27 UTC
Ended up pushing this one. Given I'm in f24/rawhide and affected by the libcue api change, I'll consider this a distcheck fix...