From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: Aaron Covrig <aaron.covrig.us@ieee.org>
Cc: tanguy@bioneland.org, me@bonfacemunyoki.com, lars@6xq.net,
jgart@dismail.de, marius@gnu.org, 75033@debbugs.gnu.org
Subject: [bug#75033] [PATCH] gnu: python-pypandoc: Fix build.
Date: Sun, 22 Dec 2024 19:21:42 +0000 [thread overview]
Message-ID: <CAO+9K5owqv90m+HbU3Lc6s_EOgfGAmnMXNowUNLy9bUukfSCLg@mail.gmail.com> (raw)
In-Reply-To: <20241222191630.1748053-1-aaron.covrig.us@ieee.org>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Hi,
Please do not revert to the python build system, just add
missing inputs - python-setuptools and python-wheel.
Check similar cases on the master branch.
Thanks,
Oleg
On Sun, 22 Dec 2024, 19:18 Aaron Covrig, <aaron.covrig.us@ieee.org> wrote:
> * gnu/packages/python-xyz.scm (python-pypandoc): Fix build
> ---
> gnu/packages/python-xyz.scm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
> index 7cf44d6b6b..217cb93fe7 100644
> --- a/gnu/packages/python-xyz.scm
> +++ b/gnu/packages/python-xyz.scm
> @@ -33714,7 +33714,7 @@ (define-public python-pypandoc
> (uri (pypi-uri "pypandoc" version))
> (sha256
> (base32 "15x161bxr7hky7rvq0jlgf1kxg6vdf069487casmpyxry7slak3b"))))
> - (build-system pyproject-build-system)
> + (build-system python-build-system)
> (arguments
> `(#:phases (modify-phases %standard-phases
> (add-before 'check 'disable-tests
>
> base-commit: 1ca065fe68d68a2fa9c3d747f23fd11c8ecfd85b
> --
> 2.46.0
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1568 bytes --]
next prev parent reply other threads:[~2024-12-22 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 19:16 [bug#75033] [PATCH] gnu: python-pypandoc: Fix build Aaron Covrig via Guix-patches via
2024-12-22 19:21 ` Sharlatan Hellseher [this message]
2024-12-23 13:30 ` [bug#75033] [PATCH v3] " Aaron Covrig via Guix-patches via
2024-12-23 17:02 ` bug#75033: [PATCH] " jgart via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO+9K5owqv90m+HbU3Lc6s_EOgfGAmnMXNowUNLy9bUukfSCLg@mail.gmail.com \
--to=sharlatanus@gmail.com \
--cc=75033@debbugs.gnu.org \
--cc=aaron.covrig.us@ieee.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=tanguy@bioneland.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).