Bug#952410: tracker-miners: FTBFS on riscv64 due to missing libseccomp build-depends

Aurelien Jarno aurel32 at debian.org
Sun Feb 23 22:17:45 GMT 2020

Source: tracker-miners
Version: 2.3.1-3
Severity: normal
Tags: patch
User: debian-riscv at lists.debian.org
Usertags: riscv64

Dear maintainer,

tracker-miners fails to build on riscv64 with the following error:

| meson.build:282:2: ERROR: Problem encountered: Libseccomp is mandatory for sandboxed metadata extraction
| dh_auto_configure: error: cd obj-riscv64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/riscv64-linux-gnu --libexecdir=lib/riscv64-linux-gnu -Dauto_features=enabled -Dgeneric_media_extractor=gstreamer -Dsystemd_user_services=/usr/lib/systemd/user -Ddocs=true -Dfunctional_tests=true -Dminer_rss=false -Dbattery_detection=upower -Dcharset_detection=icu --libexecdir=/usr/lib/tracker returned exit code 1
| make[1]: *** [debian/rules:41: override_dh_auto_configure] Error 25
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
| make: *** [debian/rules:38: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2

The full build log is available there:

libseccomp has just been made available on riscv64. I just gave it a try
and the following patch is enough to get the package building:

--- tracker-miners-2.3.1/debian/control.in      2020-01-18 21:39:59.000000000 +0000
+++ tracker-miners-2.3.1/debian/control.in      2020-02-23 21:34:04.000000000 +0000
@@ -37,7 +37,7 @@
                libosinfo-1.0-dev (>= 0.2.9),
-               libseccomp-dev (>= 2.0) [!hurd-any !kfreebsd-any !linux-alpha !linux-ia64 !linux-m68k !linux-riscv64 !linux-sh4 !linux-sparc64],
+               libseccomp-dev (>= 2.0) [!hurd-any !kfreebsd-any !linux-alpha !linux-ia64 !linux-m68k !linux-sh4 !linux-sparc64],
                dbus (>= 1.3.1) <!nocheck>,
                dbus-x11 (>= 1.3.1) <!nocheck>,
                gstreamer1.0-libav <!nocheck>,

Would it be possible to include it in the next upload?


More information about the pkg-gnome-maintainers mailing list