all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: 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, 06 Sep 2022 13:06:27 +0000	[thread overview]
Message-ID: <mPYu0RVOabPNSlkkHUhirgbiJlfzY1Inrq_1g1_RCzZPg9RXtScKNsGunaUlLbFD9dIJDp5W7rk3_LCxfuE3KaDM4fkzC4ntNpnPudTDkZU=@protonmail.com> (raw)
In-Reply-To: <NlXxYYedoJXgnGDueHeZKGCaeT3ahla6hA5zd-UTgtG0FFCW1M42mG_5Iw6nH1BHptmXGG5DEXQzSXWx-ZZ65RB7q3wI4IlsXN6dEqv63H8=@protonmail.com>

Let us not have perfect be the enemy of good, and merge the `propagated-inputs` solution. Once an `inputs` solution is found, it would be used instead.

A potential conflict with other `gnupg` instances is less harmful than the currently happening guaranteed loss of major functionality.

What do you think?




  reply	other threads:[~2022-09-06 14:43 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 [this message]
2022-09-06 15:41         ` Maxime Devos
2022-09-06 15:39       ` Maxime Devos
2022-09-06 15:44       ` Maxime Devos
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='mPYu0RVOabPNSlkkHUhirgbiJlfzY1Inrq_1g1_RCzZPg9RXtScKNsGunaUlLbFD9dIJDp5W7rk3_LCxfuE3KaDM4fkzC4ntNpnPudTDkZU=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --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.