- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 1 2025
Dec 31 2024
Dec 30 2024
Thank you. Fixed in: rPb415f3108921: build: Fix warning about obsolete pinentry-emacs.
Dec 29 2024
Dec 28 2024
Dec 27 2024
Dec 26 2024
Dec 25 2024
Dec 24 2024
Dec 23 2024
Dec 22 2024
Dec 21 2024
Dec 20 2024
Looks like gpg 2.2 doesn't emit a canceled status log message, but gpg 2.4 does if the problem only occurs with VSD but not with Gpg4win.
Actually I would like to remove the option to install gpg4win at non-standard places because this is somewhat troublesome. However some users rely on this and thus we better don't remove i.
Works, tested with VS-Desktop-3.2.94.474-Beta
What components of Gpg4win other than GnuPG do you use?
Yes, that's by design. GnuPG is always installed in $INSTDIR\..\GnuPG by the gpg4win installer.
Yeah that is a messed up environment mixing elf and windows binaries. There is no which on windows. It is called where. So if your terminal is able to execute which then this is some kind of Linux environment on Windows. The winpty error comes from the terminal. Please use cmd.exe for all tests.
The layout is totally different now in VS-Desktop-3.2.94.474-Beta but the "generate new key" action is now hidden for the slots (while still there in Gpg4win 4.4).
I just tried to call pinentry directly on Windows cmd prompt: