- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Fri, Jan 30
The gnupg manual (page 113) mentions:
Thank you for looking at this.
I'm testing with gnupg git head as of today, please let me know if you prefer 2.5.17 instead.
Thank you for your report.
TL;DR
This ticket was created because building static-linked gpgv shows warnings from glibc for getpwnam and getpwuid.
Basically, we can/should ignore the warnings from glibc at link time (for normal use cases), because it is irrelevant.
Thu, Jan 29
works in vsd 3.3.5
As a first step we should make the diagnostics output available everywhere via a button like in T6268: Kleopatra: Diagnostic output when importing keys
We have this now for VSD, there is (currently) no neccessitiy für Ggp4win
should be fixed: https://bugs.kde.org/show_bug.cgi?id=425460#c9
As there are there are no user requests for this, we'll close this
meanwhile we do not show a percentage any more so this is resolved
This has been changed by listing the other Add-Ins only if debugging is actually enabled.
This string comes from the Windows API and thus it is a Windows bug. It maye take some decades until this get fixed but at least they have meanwhile sfxed the "Westeuropäische Zeit" zu the correct "Mitteleuropäische Zeit" - Modulo Umlaut problems.
Let us mark this as a feature requests. gepwnam(3) is a standard libc function and if glibc does not support it; this is more likely a glibc bug than a bug in an application.
