From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:36420) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iKLeN-00065V-Mn for guix-patches@gnu.org; Tue, 15 Oct 2019 08:10:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iKLeM-0008Nj-Bs for guix-patches@gnu.org; Tue, 15 Oct 2019 08:10:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:34017) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iKLeM-0008Nc-8m for guix-patches@gnu.org; Tue, 15 Oct 2019 08:10:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iKLeM-0001ds-14 for guix-patches@gnu.org; Tue, 15 Oct 2019 08:10:02 -0400 Subject: [bug#37693] Seahorse build Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: Date: Tue, 15 Oct 2019 14:09:00 +0200 In-Reply-To: (Leo Prikler's message of "Thu, 10 Oct 2019 10:56:44 +0200") Message-ID: <87a7a2w6qr.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Leo Prikler Cc: 37693@debbugs.gnu.org Hi Leo, Leo Prikler skribis: > From e2b17f74841ae14ac96782539ec8bfc1c639ed34 Mon Sep 17 00:00:00 2001 > From: Leo Prikler > Date: Thu, 10 Oct 2019 10:16:47 +0200 > Subject: [PATCH] gnu: seahorse: Fix build > > * /gnu/packages/gnome.scm: (seahorse): Use meson-build-system. > Update inputs. Add patches to fix compile errors. > * /gnu/packages/patches/seahorse-fix-libsecret-breakage.patch: New file. > * /gnu/packages/patches/seahorse-fix-type-mismatches.patch: New file. Great that you were able to fix it! > - (build-system glib-or-gtk-build-system) > + "1sbj1czlx1fakm72dwgbn0bwm12j838yaky4mkf6hf8j8afnxmzp")) > + (patches > + (search-patches "seahorse-fix-libsecret-breakage.patch" > + "seahorse-fix-type-mismatches.patch")))) > + (build-system meson-build-system) Is changing the build system necessary to fix the problems you encountered, or is it a side change? From the current build log at , it does seem that the answer is =E2=80=9Cyes=E2=80=9D. :-) > (inputs > - `(("gtk+" ,gtk+) > + `(("avahi" ,avahi) > + ("gtk+" ,gtk+) > ("gcr" ,gcr) > ("gnupg" ,gnupg) > ("gpgme" ,gpgme) > @@ -2244,8 +2248,10 @@ engineering.") > (native-inputs > `(("intltool" ,intltool) > ("glib:bin" ,glib "bin") > + ("gtk+:bin" ,gtk+ "bin") > ("itstool" ,itstool) > ("pkg-config" ,pkg-config) > + ("vala" ,vala) Likewise, these changes were necessary, right? > diff --git a/gnu/packages/patches/seahorse-fix-libsecret-breakage.patch b= /gnu/packages/patches/seahorse-fix-libsecret-breakage.patch > new file mode 100644 > index 0000000000..d6396c227a > --- /dev/null > +++ b/gnu/packages/patches/seahorse-fix-libsecret-breakage.patch [...] > --- /dev/null > +++ b/gnu/packages/patches/seahorse-fix-type-mismatches.patch > @@ -0,0 +1,154 @@ > +From 12178d7cc7fad52f61003b3221bd0a713ef80507 Mon Sep 17 00:00:00 2001 > +From: Rico Tzschichholz > +Date: Mon, 5 Nov 2018 09:59:27 +0100 > +Subject: [PATCH] Fix type-argument mismatches related to GLib.List One last thing: are those patches upstream, or is there a bug report where they were discussed? If so could you share the URLs? I can add them on your behalf in the .patch file if you want. That=E2=80=99ll allow us to better keep track of = where our patches come from and when we can remove them. Thanks! Ludo=E2=80=99.