- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Tue, Oct 28
Mon, Oct 27
Workaround is to use --with-keygrip and delete both <keygrip>.key files. Problem here is that one part may be on a smartcard or one part might be shared (although not allowed) with other keys.
Fri, Oct 24
But you are able to do this w/o gpgol being active?
Thu, Oct 23
gpgconf does not know about the global config files. Nor does it known about things like gpg.conf-2 etc.
Wed, Oct 22
I'd sad we keep it as it is now (unless we see a regression). The real and only correct solution is the use of a daemon to serialize access.
Tue, Oct 21
That might be related to T2196 which has been hopefully fixed in 2.2.50 and also in the next 2.6. Closing this task.
That might be related to T2196 which has been hopefully fixed in 2.2.50 and also in the next 2.6. Closing this task.
I applied it to the 2.4 branch but please do not continue to translate for 2.4. 2.6 (master) is the new target.
Implemented but not tested at all.