emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53679: closed ([PATCH] gnu: fontmanager: depend on python3)


From: GNU bug Tracking System
Subject: bug#53679: closed ([PATCH] gnu: fontmanager: depend on python3)
Date: Thu, 24 Feb 2022 02:55:02 +0000

Your message dated Wed, 23 Feb 2022 21:54:36 -0500
with message-id <877d9lm0sz.fsf_-_@gmail.com>
and subject line Re: bug#53679: [PATCH] gnu: fontmanager: depend on python3
has caused the debbugs.gnu.org bug report #53679,
regarding [PATCH] gnu: fontmanager: depend on python3
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53679: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53679
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] gnu: fontmanager: depend on python3 Date: Mon, 31 Jan 2022 21:55:12 -0800
This package requires python3 on the path to sucessfully build:

    Program python found: NO
    ../source/meson.build:45:0: ERROR: python3 not found

* gnu/packages/fontutils.scm (fontmanager)[inputs]: Add python-3
---
 gnu/packages/fontutils.scm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gnu/packages/fontutils.scm b/gnu/packages/fontutils.scm
index bc082de3d3..5a92f752d1 100644
--- a/gnu/packages/fontutils.scm
+++ b/gnu/packages/fontutils.scm
@@ -906,6 +906,7 @@ (define-public fontmanager
       ("gtk+" ,gtk+)
       ("json-glib" ,json-glib)
       ("libsoup" ,libsoup-minimal-2)
+      ("python" ,python-3)
       ("sqlite" ,sqlite)
       ("webkitgtk" ,webkitgtk-with-libsoup2)))
    (home-page "https://fontmanager.github.io/";)
-- 
2.34.0




--- End Message ---
--- Begin Message --- Subject: Re: bug#53679: [PATCH] gnu: fontmanager: depend on python3 Date: Wed, 23 Feb 2022 21:54:36 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hello,

Julien Lepiller <julien@lepiller.eu> writes:

> Hi, I believe I fixed this very issue yesterday. Can you confirm?
>
> Also, when adding a tool that is used during the build, you should use
> native-inputs instead, or cross-builds will fail.

Works fine for me, after adding gsettings-desktop-schemas as an input in
45d0c82dcc7380e78472dd819981a5025f6157e5 (otherwise I'd get a error due
to a missing schema on my non-GNOME machine).

Closing.

Thanks!

Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]