Hi @DemiMarie , thank you for this quick response.
can you confirm that import works in recent versions for this key?
```bash
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GopenPGP 2.4.10
Comment: https://gopenpgp.org
xsFNBGOXVycBEAC1WtGnRGw5/X6g3O46sC6gF4CDgdsX6/ny9phr5ptZLZP4pX5q
Please report this to SUSE. RPM 4.14.3 won’t be getting updates from upstream.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2323#issuecomment-1347608828
You are receiving this because you are subscribed to this thread.
Message ID:
Hi,
I try to debug an issue we ran into while trying to import GPG keys generate
using GO https://github.com/ProtonMail/go-crypto
The sub package type "Issuer ID" is always set "critical":
Thank you! Very helpful!
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2322#discussioncomment-4380465
You are receiving this because you are subscribed to this thread.
Message ID:
___
The regular user doesn't have write-permissions on the shared database
environment (those __db.* files), which is required to register even a
read-lock in there. So when running as a regular user, rpm cheats by using a
private environment, which amounts to no locking at all wrt a concurrent
I really don't remember the behavior from those days, no strong opinion here.
Other than agreeing on "it seems pretty broken in many places" that is.
As for optflags - yes, and BuildArch should arguably also (re)load platform
macros while at it.
--
Reply to this email directly or view it on
Oh, that db_recovery stuff is only relevant for Berkeley DB backend, and in
upstream configuration. On Suse, the BDB usage differs and you wouldn't see
such messages (IIRC). Also 4.14 fell out of upstream support a couple of years
ago already.
The db_recovery doc needs to be updated though.
