From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New Packages: sequoia cli utilities
Date: Wed, 21 Sep 2022 12:23:13 +0200 [thread overview]
Message-ID: <20220921102313.Kcs-nN465UmCD6-3-LbM3OkGzAJ4vRjZU6hxeQO0Vhk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32480@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
There's a merged pull request on the void-packages repository
New Packages: sequoia cli utilities
https://github.com/void-linux/void-packages/pull/32480
Description:
#### 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)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
### TODO
- [x] sq
- [x] sqop
- [x] sqv
- [x] add man pages
- [x] figure out cross compiling (was broken due to nettle-dev being required on the host as well as the target)
- ~~add shell completions~~ will be done after https://gitlab.com/sequoia-pgp/sequoia/-/issues/798 is fixed.
- [x] tell upstream about adding git tags for openpgp-card-tools ([upstream issue](https://gitlab.com/hkos/openpgp-card/-/issues/32))
- ~~figure out building for armv7l (some lib stuff missing, see [log](https://web.archive.org/web/20220409160215/https://pipelines.actions.githubusercontent.com/serviceHosts/8d180b0e-8647-44ca-8431-6b9f11113866/_apis/pipelines/1/runs/49556/signedlogcontent/6?urlExpires=2022-04-09T16%3A02%3A59.1606901Z&urlSigningMethod=HMACV1&urlSignature=gkM%2FhddrZEYzNMnQZqSFJQcD3ARwMfWvTQLNQA30A9g%3D))~~ marked as nocross for armv7l for now, considering neither we nor upstream really know *why* it's failing to cross compile
- [x] figure out building for x86_64-musl (some deprecated musl specific rust code, see [log](https://web.archive.org/web/20220409160239/https://pipelines.actions.githubusercontent.com/serviceHosts/8d180b0e-8647-44ca-8431-6b9f11113866/_apis/pipelines/1/runs/49556/signedlogcontent/8?urlExpires=2022-04-09T16%3A03%3A21.7631273Z&urlSigningMethod=HMACV1&urlSignature=iRYCydXZC%2FxRhVp8pVRbPgkAk8puf85yX5uMTGmzcGM%3D))
prev parent reply other threads:[~2022-09-21 10:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 14:11 [PR PATCH] " jcgruenhage
2021-08-13 16:13 ` [PR PATCH] [Updated] " jcgruenhage
2021-08-13 16:16 ` jcgruenhage
2021-08-13 16:55 ` jcgruenhage
2022-01-15 15:32 ` jcgruenhage
2022-02-08 14:42 ` jcgruenhage
2022-02-08 22:14 ` jcgruenhage
2022-02-21 5:00 ` jcgruenhage
2022-02-26 18:30 ` jcgruenhage
2022-04-09 14:54 ` jcgruenhage
2022-04-09 15:18 ` [PR REVIEW] " classabbyamp
2022-04-09 15:28 ` jcgruenhage
2022-04-09 16:05 ` jcgruenhage
2022-05-14 9:43 ` jcgruenhage
2022-05-14 9:46 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-15 21:32 ` ericonr
2022-05-15 22:43 ` classabbyamp
2022-06-02 9:12 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-02 9:46 ` jcgruenhage
2022-06-03 9:54 ` jcgruenhage
2022-06-14 12:10 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-14 12:47 ` jcgruenhage
2022-06-14 14:10 ` jcgruenhage
2022-06-14 14:20 ` jcgruenhage
2022-08-01 14:57 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-07 16:38 ` jcgruenhage
2022-08-08 20:32 ` jcgruenhage
2022-08-08 21:16 ` [PR REVIEW] " classabbyamp
2022-08-08 21:16 ` classabbyamp
2022-08-09 8:54 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-09 22:24 ` jcgruenhage
2022-08-09 23:19 ` jcgruenhage
2022-08-09 23:25 ` jcgruenhage
2022-08-12 6:41 ` [PR REVIEW] " ericonr
2022-08-12 7:42 ` jcgruenhage
2022-08-12 17:45 ` ahesford
2022-09-21 10:23 ` ahesford [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=20220921102313.Kcs-nN465UmCD6-3-LbM3OkGzAJ4vRjZU6hxeQO0Vhk@z \
--to=ahesford@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).