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 794313 - gnome-control-center FTBFS: Could not generate cargs for gnome-bluetooth-1.0
gnome-control-center FTBFS: Could not generate cargs for gnome-bluetooth-1.0
Status: RESOLVED NOTGNOME
Product: gnome-bluetooth
Classification: Core
Component: general
3.28.x
Other Linux
: Normal major
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
gnome-bluetooth-general-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2018-03-14 02:14 UTC by Jeremy Bicha
Modified: 2018-03-22 16:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2018-03-14 02:14:03 UTC 
Ubuntu 18.04
meson 0.45.0

gnome-control-center 3.28.0 fails to build from source with gnome-bluetooth 3.28.0. The build succeeds with gnome-bluetooth 3.27.90.


Build log excerpt
=================
Native dependency libnm found: YES 1.10.4
Native dependency libnma found: YES 1.8.10
Native dependency mm-glib found: YES 1.6.8
Native dependency NetworkManager found: YES 1.10.4

meson.build:212:2: ERROR: Could not generate cargs for gnome-bluetooth-1.0:
Comment 1 Jeremy Bicha 2018-03-15 02:13:46 UTC 
The meson error was frustratingly imprecise.

The problem was triggered because gnome-bluetooth 3.28.0 (and I assume 3.27.92)
added this line to its pkgconfig file:

  Requires.private: gmodule-2.0 libcanberra-gtk3 gio-unix-2.0 libudev libnotify

Debian's libgnome-bluetooth-dev was missing a dependency on libnotify-dev.
Comment 2 Jeremy Bicha 2018-03-15 02:17:05 UTC 
I wonder if meson 0.45.0 introduced this change?
Comment 3 Bastien Nocera 2018-03-22 15:27:22 UTC 
FWIW, I use meson 0.44.0, and I didn't have problems building gnome-control-center. It might just be that libnotify-dev was pulled in by something else in the stack below before, and not anymore.
Comment 4 Jeremy Bicha 2018-03-22 16:04:44 UTC 
It was a meson 0.45 change. For much more detail, see https://bugs.debian.org/892956

Anyway, nothing to fix in GNOME, but it's useful to know what that cargs error could mean.