We will keep the 1.24 branch for bug fixing. Do you really have a problem with gpgme 2.0? Ist that due to factoring out the c++ and qt bindings? That was actually a long standing request from the KDE community so that they can use their cmake stuff.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 5 2025
I'm wondering whether gpgme v1 will still be supported? Or it will be abandoned from now on.
Jun 3 2025
Jun 2 2025
May 27 2025
May 23 2025
May 20 2025
May 19 2025
Noet that one file is missing in the released tarball; when building for RISC-V please see T7647#201164
May 9 2025
May 8 2025
May 7 2025
Apr 24 2025
Apr 17 2025
Apr 9 2025
Note that 1.53 was released today which fixes a small regression:
Apr 8 2025
Mar 25 2025
Mar 7 2025
Feb 18 2025
Feb 12 2025
Feb 10 2025
Jan 23 2025
Jan 22 2025
In case of build problems related to a failed test you may want to apply rEb6df311368133df90c3bf338fbf5c90bd8d950f8.
Jan 14 2025
Note: The is a bug in the gnupg-w32-2.5.3 tarballs. After untaring cd to the directory as usual but then do:
rm PLAY/src/zlib/*.[oa] PLAY/src/bzip2/*.[oa]
before you run
make -f build-aux/speedo.mk this-native
Jan 10 2025
Jan 9 2025
i see the tag has been published now, thanks! Given that this is an ELTS release, I'm assuming that the lack of a gnupg-2.2.46.tar.bz2 file on https://gnupg.org/ftp/gcrypt/gnupg/ is deliberate.
Jan 8 2025
will you tag 2.2.46 in git as well? it appears to be on rG7e48331afb611a2b39e5ae74b8806b84e54db924 but i don't see any tags.
Jan 7 2025
Jan 6 2025
Dec 10 2024
Dec 5 2024
Dec 4 2024
Nov 28 2024
Nov 25 2024
Nov 12 2024
Nov 11 2024
Nov 7 2024
Nov 6 2024
Oct 29 2024
Oct 22 2024
See T7255 instead.