Your message dated Wed, 7 Jun 2017 13:56:06 -0400
with message-id
<CAAajCMY8zjjrwoJz+pcd8OEZE=M07YcMMV36WpQqjvtu4kg=x...@mail.gmail.com>
and subject line Re: debhelper: meson "failed to to execute"
has caused the Debian Bug report #864369,
regarding debhelper: meson "failed to to execute"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
864369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864369
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debhelper
Version: 10.4
I am trying to use debhelper's new meson support to build a new
version of gnome-tweak-tool but it's failing. It obviously works for
some other packages though.
https://git.launchpad.net/~jbicha/gnome-tweak-tool
dh build --with gnome,python3 --buildsystem=meson
dh_testdir -O--buildsystem=meson
dh_update_autotools_config -O--buildsystem=meson
dh_autoreconf -O--buildsystem=meson
dh_auto_configure -O--buildsystem=meson
meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr
--sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu
--libexecdir=lib/x86_64-linux-gnu
dh_auto_configure: meson .. --wrap-mode=nodownload --buildtype=plain
--prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu failed
to to execute: No such file or directory
debian/rules:6: recipe for target 'build' failed
Other Info
---------------
Technically, I am using Ubuntu's debhelper 10.4ubuntu3 which is very
similar to Debian's version with a few git patches backported.
I tried adding a meson_options.txt in case debhelper wanted that but
that didn't seem to make a difference. I guess the problem is figuring
out what file debhelper/meson is trying to execute.
Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Oops, this was my fault.
My host is still running Ubuntu 17.04 and I didn't update my
debhelper. I told sbuild to run without cleaning (since otherwise it
would fail when it saw the meson stuff). But I hadn't updated
debian/control to match debian/control.in yet (which wouldn't have
mattered much had debhelper clean ran before building).
Thanks,
Jeremy
--- End Message ---
