Hi Farblos--
On Tue 2024-05-14 21:28:05 +0200, Farblos wrote:
> Should I open another issue about PINENTRY_USER_DATA not being
> forwarded to the pinentry when using the gpg from package gpg-sq/
> gpg-from-sq? If yes, on what repository exactly?
I would report it at
Hi Daniel,
On 2024-05-08 19:25, Daniel Kahn Gillmor wrote:
thanks for taking care about this in general and this one:
> Thanks, i've reported this part upstream:
> https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/74
in particular.
Should I open another issue about
Control: affects 1070688 + gpg-from-sq apt
Hi Farblos, all--
Thanks for this detailed bug report (https://bugs.debian.org/1070688).
I'm a bit confused about the following:
On Wed 2024-05-08 11:07:28 +0200, Farblos wrote:
> Never mind. During one of the last t64 upgrade orgies package gpg-sq
Never mind. During one of the last t64 upgrade orgies package gpg-sq got
installed on my system and succeeded to install the diversion to /usr/bin/gpg.
And the sequoia replacement is not very feature complete, as they continue
to stress themselfes.
For example, referencing a recipient by exact
A quick comparison of the package sources hasn't revealed anything obvious.
So here is a reproducer (custom pinentry defined in gpg-agent.conf that dumps
its environment):
[~]$ grep ^pinentry-program .gnupg/gpg-agent.conf
pinentry-program/home/farblos/tmp/pinentry
[~]$ cat
Package: gnupg
Version: 2.2.40-3
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
Most likely today's upgrade from GnuPG related packages
2.2.40-1.1 -> 2.2.40-3. "Yesterday this still has been working."
* What exactly did you do (or
6 matches
Mail list logo
