Thanks for the comments. This is a regular git for Windows install which afaik uses mingw64. The messup with the binaries brought in by git has always been this way. I am using aliases to differentiate between the different versions. One might think that this may cause things to break, however all used to work well with 4.x versions.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 20 2024
gpg: [stdin]: clear-sign failed: No pinentrysrc/libwinpty/winpty.cc, line 924
Here you are:
This problem has gone in libgpg-error 1.51, since the implementation doesn't use environ any more.
Dec 19 2024
Installing language-pack-tr-base fixed the issue. Closing. Sorry for the noise.
Works. Tested with VS-Desktop-3.2.94.474-Beta and Gpg4win 4.4 by moving only the signature key to a smartcard and then changing the password of the certificate via the context menu.
Dec 18 2024
In T7454#196228, @werner wrote:Actually not a bug: In my tests I forgot to unset LANGUAGES and LANG before calling gpg.
LANGUAGE= LANG= LC_MESSAGES=de_DE gpgThus this should work. But it did only work when I used
LANGUAGE= LANG= LC_MESSAGES=de_DE.UTF8 gpgThus the whole thing is related to the configuration of locale.alias and on whether LANGUAGE is set in the environment (for me it is set to en_US:en
Actually not a bug: In my tests I forgot to unset LANGUAGES and LANG before calling gpg.
I can replicate this. A quick strace with LC_MESSAGES=de_DE shows (gnupg master)
Backported for VSD 3.3.
Another data point:
$ locale LANG=de_DE.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL=
Are you sure that the translations for gnupg are installed? On Tumbleweed translations are usually in a separate package. After installing the gpg2-lang package I get this when I force the Turkish translation:
$ LANGUAGE=tr_TR gpg --version gpg (GnuPG) 2.5.2 libgcrypt 1.11.0 Copyright (C) 2024 g10 Code GmbH License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
In T7454#196094, @werner wrote:Does
gpg --versionshow English or Turkish strings?
Dec 17 2024
Thanks for opening the ticket. I looked at it when it was reported in the forum, But had no test build at hand to test a fix. If you look at the history of g4wihelp.c you can see how other functions have been ported to Unicode recently. The change is that the strings in the nsis script world have changed to two byte strings. The problem is then where the c code interacts with the NSIS script obtaining parameters and setting return values. Since the popstackna takes an ascii string it only takes the first character as the second byte is null. Changing these occurrences to popstackn and the setuservariable to widechar should do the trick.
FWIW: as mentioned in T7452#195891, it might be necessary to manually copy the uninstaller to a temporary directory ({{ tmp_uninstall_exe }}) and call it from there to get a clean uninstall: