From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
Cc: 58386-done@debbugs.gnu.org, ngraves@ngraves.fr,
58340@debbugs.gnu.org, 58340-done@debbugs.gnu.org
Subject: [bug#58340] bug#58386: [PATCH v2] gnu: Add passage.
Date: Wed, 19 Oct 2022 21:49:50 +0200 [thread overview]
Message-ID: <87czanbneo.fsf@nckx> (raw)
In-Reply-To: <87h6zzbo14.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
Tobias Geerinckx-Rice via Guix-patches via 写道：
> …but in this case, I was bold and removed the two
> go-filippo-io-cmd-age* packages completely.
Grr. And of course, whilst migrating pass-age's propagated-inputs
to regular ones (propagation is evil and should be avoided
whenever possible), I see I've been looking at the wrong ‘age’.
Y'know. The one that does have a ‘/bin/age’ in it.
Yep, I'm back,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-19 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 22:42 [bug#58386] Age encryption : passage Nicolas Graves via Guix-patches via
2022-10-08 22:44 ` [bug#58386] [PATCH 1/2] gnu: passage: Rename package to passage-game Nicolas Graves via Guix-patches via
2022-10-08 22:44 ` [bug#58386] [PATCH 2/2] gnu: Add passage Nicolas Graves via Guix-patches via
2022-10-08 23:05 ` Tobias Geerinckx-Rice via Guix-patches via
2022-10-11 21:39 ` [bug#58386] [PATCH v2] " Nicolas Graves via Guix-patches via
2022-10-19 17:17 ` bug#58340: " Tobias Geerinckx-Rice via Guix-patches via
2022-10-19 19:49 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-10-22 7:51 ` [bug#58340] bug#58386: " Nicolas Graves via Guix-patches via
2022-10-19 19:54 ` bug#58457: " Tobias Geerinckx-Rice 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czanbneo.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=58340-done@debbugs.gnu.org \
--cc=58340@debbugs.gnu.org \
--cc=58386-done@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=ngraves@ngraves.fr \
/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.