From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: prs-0.3.2
Date: Sun, 26 Jun 2022 23:16:51 +0200 [thread overview]
Message-ID: <20220626211651.YmQfpujm0NnxdQu0OgCyeOF4iXy4S-gsWM_rSHJmh9E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29593@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
There's a merged pull request on the void-packages repository
New package: prs-0.3.2
https://github.com/void-linux/void-packages/pull/29593
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
<del>This is currently sort-of broken. `prs` supports multiple backends, and the default is to use the `gpg` binary, which is broken, because unlike other
distros, Void doesn't ship gnupg2 as `gpg`. Maybe we should add alternatives to gnupg2 and gnupg to allow both as the `gpg` binary?</del>
prev parent reply other threads:[~2022-06-26 21:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 16:37 [PR PATCH] WIP: New package: prs-0.2.4 jcgruenhage
2022-03-22 23:10 ` 0x5c
2022-03-22 23:37 ` jcgruenhage
2022-03-22 23:49 ` 0x5c
2022-03-26 16:37 ` [PR PATCH] [Updated] " jcgruenhage
2022-03-26 16:39 ` [PR PATCH] [Updated] New package: prs-0.3.2 jcgruenhage
2022-03-26 16:40 ` jcgruenhage
2022-03-26 21:03 ` [PR PATCH] [Updated] " jcgruenhage
2022-03-26 22:11 ` 0x5c
2022-03-27 7:24 ` jcgruenhage
2022-03-27 10:00 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-26 2:15 ` github-actions
2022-06-26 10:26 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-26 10:27 ` jcgruenhage
2022-06-26 21:16 ` Duncaen [this message]
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=20220626211651.YmQfpujm0NnxdQu0OgCyeOF4iXy4S-gsWM_rSHJmh9E@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).