From: dshynkev <dshynkev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gopass: update to 1.11.0.
Date: Sun, 24 Jan 2021 23:00:22 +0100 [thread overview]
Message-ID: <20210124220022.88lYutIixVvfBxduRSnHhoBi9P_QDiRCDKwaeiNaTJQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28202@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
New comment by dshynkev on void-packages repository
https://github.com/void-linux/void-packages/pull/28202#issuecomment-766439616
Comment:
One thing of note: this version changed the way the `gpg` binary is selected. They assume `gpg` points to the version of GPG the user uses, but on Void it points to GPG v1, which is probably not what most use.
One must `export GOPASS_GPG_BINARY=$(which gpg2)` for it to keep working with GPG v2.
Should I note this in a post-install message?
next prev parent reply other threads:[~2021-01-24 22:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 21:55 [PR PATCH] " dshynkev
2021-01-24 21:59 ` dshynkev
2021-01-24 22:00 ` dshynkev [this message]
2021-01-24 23:02 ` ericonr
2021-01-25 0:27 ` dshynkev
2021-01-25 0:27 ` dshynkev
2021-01-25 0:28 ` [PR PATCH] [Updated] " dshynkev
2021-01-25 1:33 ` ericonr
2021-01-25 12:54 ` ahesford
2021-01-25 13:29 ` ericonr
2021-01-25 23:26 ` [PR REVIEW] " ericonr
2021-01-27 7:46 ` [PR PATCH] [Updated] " dshynkev
2021-01-27 7:48 ` [PR REVIEW] " dshynkev
2021-01-27 15:02 ` [PR PATCH] [Updated] " dshynkev
2021-01-27 15:08 ` ahesford
2021-01-27 15:08 ` ahesford
2021-01-27 15:20 ` [PR PATCH] [Updated] " dshynkev
2021-01-27 15:22 ` dshynkev
2021-02-02 18:47 ` ahesford
2021-02-11 20:30 ` [PR PATCH] [Updated] " dshynkev
2021-02-11 20:31 ` gopass: update to 1.12.0 dshynkev
2021-02-11 21:23 ` [PR PATCH] [Merged]: " ericonr
2021-01-25 22:44 [PR PATCH] gopass: update to 1.11.0 kkga
2021-01-25 23:24 ` ericonr
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=20210124220022.88lYutIixVvfBxduRSnHhoBi9P_QDiRCDKwaeiNaTJQ@z \
--to=dshynkev@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).