From: Maxime Devos <maximedevos@telenet.be>
To: "Marek Paśnikowski" <marekpasnikowski@protonmail.com>,
"Efraim Flashner" <efraim@flashner.co.il>
Cc: Ricardo Wurmus <rekado@elephly.net>,
"57345@debbugs.gnu.org" <57345@debbugs.gnu.org>
Subject: [bug#57345] [PATCH] Add gnupg to propagated-inputs of trezor-agent
Date: Tue, 6 Sep 2022 17:44:34 +0200 [thread overview]
Message-ID: <5651ad51-13cf-a535-143a-f1bf1d791881@telenet.be> (raw)
In-Reply-To: <NlXxYYedoJXgnGDueHeZKGCaeT3ahla6hA5zd-UTgtG0FFCW1M42mG_5Iw6nH1BHptmXGG5DEXQzSXWx-ZZ65RB7q3wI4IlsXN6dEqv63H8=@protonmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 476 bytes --]
On 05-09-2022 13:26, guix-patches--- via wrote:
> I have encountered the same problem as in this email:
> https://lists.gnu.org/archive/html/help-guix/2019-06/msg00073.html
>
> I do not understand how to apply the proposed fix.
>
IIRC, python-build-system uses G-exps nowadays, so to use #$, all you
need to do is replace
(arguments `(#:phases (modify-phases ...)))
by
(arguments (list #:phases #~(modify-phases ...))),
no need for separate inputs.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-06 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:03 [bug#57345] [PATCH] Add gnupg to propagated-inputs of trezor-agent guix-patches--- via
2022-09-01 8:51 ` Ricardo Wurmus
2022-09-05 5:49 ` guix-patches--- via
2022-09-05 9:25 ` Efraim Flashner
2022-09-05 11:26 ` guix-patches--- via
2022-09-06 13:06 ` guix-patches--- via
2022-09-06 15:41 ` Maxime Devos
2022-09-06 15:39 ` Maxime Devos
2022-09-06 15:44 ` Maxime Devos [this message]
2022-09-06 15:48 ` Maxime Devos
2022-09-09 19:55 ` guix-patches--- via
2022-10-11 14:44 ` [bug#57345] (No Subject) Attila Lendvai
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=5651ad51-13cf-a535-143a-f1bf1d791881@telenet.be \
--to=maximedevos@telenet.be \
--cc=57345@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=marekpasnikowski@protonmail.com \
--cc=rekado@elephly.net \
/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.