On Sun 2025-02-09 14:54:59 +0100, Andreas Metzler wrote:
> That makes perfectly good sense. How about waiting a week or so for
> feedback on this on the upstream report?
Sure, that works for me. If you have any other ideas or suggestions in
the meantime, i'd be happy to talk them over too.
-
On 2025-02-08 Daniel Kahn Gillmor wrote:
> On Sat 2025-02-08 07:35:41 +0100, Andreas Metzler wrote:
> > Andreas Klode gave us a heads-up about this in
> > https://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/2024-March/009235.html
> > | after a report of gnupg 2.4 breaking some tooling in Ub
Control: clone 1095451 -1
Control: retitle -1 With use-keyboxd, gpg ignores all --keyring arguments
Control: reopen -1
Control: found -1 2.4.7-4
Control: forwarded -1 https://dev.gnupg.org/T7265
On Sat 2025-02-08 07:35:41 +0100, Andreas Metzler wrote:
> Andreas Klode gave us a heads-up about this
On 2025-02-08 Daniel Kahn Gillmor wrote:
> Package: gpg
> Version: 2.4.7-3
> Severity: normal
> The 2.4 series of GnuPG introduces keyboxd, but doesn't force migration
> to it for existing users.
> For new users, however, running without an explicitly set $GNUPGHOME,
> /usr/bin/gpg creates ~/.gn
Package: gpg
Version: 2.4.7-3
Severity: normal
The 2.4 series of GnuPG introduces keyboxd, but doesn't force migration
to it for existing users.
For new users, however, running without an explicitly set $GNUPGHOME,
/usr/bin/gpg creates ~/.gnupg and populates it with a single file,
common.conf, wh
5 matches
Mail list logo