- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 23 2022
Sep 20 2022
Sorry, you need to wait for gnupg 2.3.8. It's next on our shortlist.
Sep 19 2022
May 22 2022
Mar 7 2022
Should be fixed.
Mar 6 2022
The patch for T5834 (https://dev.gnupg.org/rMad3aabdd8a64156c7e3a75d695ae1ab2c4bec841) was already applied to the build of GPGME 1.17.0 for Focal, as I did browse the list of latest GPGME bugs first before reporting this bug. Attempting to build with the latest GPGME 1.17.1 (with the included ABI patch) results in exactly the same FTBFS for i386 only, so this does appear to be a distinct issue not related to that of ABI backwards compatibility.
Please see T5834 which is fixed in 1.17.1
Sep 21 2021
Please see T5587
Aug 13 2021
Feb 1 2021
to explain a bit more: This report was opened after the reported defect was already fixed.
As we are getting many reports and technical suggestions, please keep the reports focused on one point only if possible
and open general discussion points about development improvements on gnupg-devel@.
For what it is worth we have also just tasked someone from our team to reinstate our buildbot / CI but this would likely not have helped in the current case of the libgcrypt buffer error as only ASAN with large hashtests would have found this. Still we have the general infrastructure for such tests we are just lacking resources. That is why we publish everything and encourage the community to at least help us with testing.
the issue regarding this self test was immediately found after release. Our development is completely open and everyone is free to run tests with our software on any platform at any time. We would respect and fix all those bug reports. None about this reached us during the development phase.
As this is not happening as it should during development we release and test on our platforms and build systems. When after the release others test, too we immediately fix the issues as happened with 1.9.1 in libgcrypt.
Jan 29 2021
@hanno, this is a bug tracker and not yet another media for your rants.
Dec 11 2020
Jul 14 2020
Feb 6 2020
It has been fixed in the repo for nearly a year, see T4459. A new release is urgently required and will follow in the next days. I close this as a duplicate.
Dec 7 2019
In T1287#94619, @werner wrote:2.1 has the option --unwrap to just this.
Jun 26 2019
May 10 2019
We fixed this bug already in the repo. See T4459.