all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: ryan@arctype.co, 53679@debbugs.gnu.org
Subject: [bug#53679] [PATCH] gnu: fontmanager: depend on python3
Date: Tue, 01 Feb 2022 09:13:23 +0100	[thread overview]
Message-ID: <794D5F18-6369-4C17-9911-DEF294C6B6D0@lepiller.eu> (raw)
In-Reply-To: <20220201055512.6391-1-ryan@arctype.co>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

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.

On February 1, 2022 6:55:12 AM GMT+01:00, Ryan Sundberg via Guix-patches via <guix-patches@gnu.org> wrote:
>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
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1441 bytes --]

  reply	other threads:[~2022-02-01  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  5:55 [bug#53679] [PATCH] gnu: fontmanager: depend on python3 Ryan Sundberg via Guix-patches via
2022-02-01  8:13 ` Julien Lepiller [this message]
2022-02-24  2:54   ` bug#53679: " Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=794D5F18-6369-4C17-9911-DEF294C6B6D0@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=53679@debbugs.gnu.org \
    --cc=ryan@arctype.co \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.