I think we should close this bug or re-purpose it to silence those warnings in common cases.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 29 2024
Feb 23 2024
That could be fixed in src/argparse.c:set_opt_arg by adding and endptr to the strtol calls and check that only white space follows. However, there is some risk of regression with this approach. Maybe just display a warning?
With today's release of npth everything should be set.
Feb 6 2024
Feb 1 2024
Thank you for the fix. Pushed the change modifying the commit log for the ChangeLog entry.
Jan 31 2024
Jan 23 2024
Jan 22 2024
Jan 16 2024
Alright.
Push the change as rE4a9def77488f: estream: Fix call to string filter for estream-printf..
I see your point: allocating STRINGBUF to make sure nul-terminated string.
The code itself doesn't work well in a test case of tests/t-prinntf.c, because it assumes string filter should be called with NULL for string.
Jan 15 2024
Like this:
@@ -1196,10 +1196,25 @@ pr_string (estream_printf_out_t outfnc, void *outfncarg, future, when breaking API/ABI is OK, we can change signature of gpgrt_string_filter_t to have another argument for precision. */ int allow_non_nul_string = (arg->precision >= 0); + char *stringbuf = NULL;
We could also pass a nul terminated copy to the filter function in pr_string.
Dec 27 2023
Nov 15 2023
@item handling with @table has been pushed.
Nov 14 2023
I learned about how @item is handled by TeX. By @table command, user specifies how to handle the item line. In the case of GnuPG, it is like:
@table @gnupgtabopt @item --version ... @item --help
(Emacs uses @table @samp, while GCC uses @table @gcctabopt.)
And @gnupgtabopt is a macro which is expanded to @code{\body\}
Nov 8 2023
Possible approach for source texinfo files and yat2m would be:
Nov 2 2023
I found a regression for @item --version; It emits \[en]version for roff.
Pushed my fix to support them.
Oct 5 2023
Sep 30 2023
I guess we should add an extended API to set the filter.
Sep 27 2023
Sep 26 2023
Aug 31 2023
I guess we should follow the GNU standards and provide only info files ;-)
Other problems of yat2m transformation:
https://bugs.debian.org/1050886
Aug 28 2023
Not easy do decide whether something is a PIN or a PUK and we will need to check a lot of places. So, not now.
Aug 25 2023
Aug 22 2023
I found a troff reference: https://www.quut.com/berlin/ms/troff.html
Ideally, we should change the source document to use @minus{} for a minus sign, and keep - only when it means a hyphen. But we cannot do that blindly; We need to handle it with care, in a way of case by case (Texinfo manual suggests no use of @minus{} with @code or @example, but it is needed for groff man pages in many cases).... We would need to consider each occurrence of - in our document. That's too much (if it were me to fix).
Aug 18 2023
Pushed the change to:
- libgpg-error
- libassuan master
- libgcrypt master
- ntbtls
- npth
- libksba
- gpgme
- scute
Aug 16 2023
It looks to me like it's marginally more common to *not* use the lib prefix for pkgconfig files:
Aug 14 2023
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Aug 7 2023
Aug 2 2023
I pushed the commit: rE64532db11fcd: build: New configure option --with-libtool-modification.
Jul 28 2023
Pushed the change to libgpg-error.
Jul 27 2023
That assumes that libtool won't change substantially as it did several times in the past and broke our cross compiling stuff. But as long as we keep the ltmain.sh in our repo and tarball the patch is okay because it better documents the chnages.
I learned that AC_CONFIG_COMMANDS macro can be used to improve the case of config.status.
How about the change like:
Jul 24 2023
I have built it according to the method described here.
(https://wiki.documentfoundation.org/Development/BuildingOnWindows)
I wonder why you mention Visual Studio and Cygwin? Either it is Cygwin or a native Windows build.
Jul 13 2023
Jun 2 2023
May 26 2023
May 12 2023
Pushed to GnuPG master. Let us test. For my machine of Debian GNU/Linux, Wine emulation (Windows 32-bit, Windows 64-bit), make check goes all well.
After confirming the implementation, I'd like to put it into gpgrt.
May 1 2023
Apr 27 2023
I learned that Unix build environment needs Wine emulation (with winepath) for MinGW host (when uninstalled executable should run correctly).
https://www.gnu.org/software/libtool/manual/html_node/File-name-conversion.html
Apr 13 2023
Apr 10 2023
Fixed in 1.47.
Fixed in libgcrypt 1.10.2.
Fixed in libgpg-error 1.47.
Apr 7 2023
Fixed in 1.10.2.
Apr 6 2023
In T6388#168750, @gniibe wrote:Thank you for the bug report.
I see your problem. We need to improve the patch, as we cannot use Bash-only feature in configure.
[...]
That is, prefer possible_libdir1 when not used. Please test this.
I'll add new error codes to gpgrt
Apr 4 2023
Any volunteers to write a manual? ;-)
The reason may be the following text/comment I found in gpgrt.texi:
This manual documents the Libgpg-error library application programming
interface (API). The goal is to that all functions and data types
provided by the library are explained. However, for now this is only
a stub and not very useful.
Mar 28 2023
Mar 25 2023
@tlaurion Thank you for the report, but your particular problem is irrelevant to this ticket.
I lightly looked the log and noticed that the cross build would have some confusions for pkg-config, however, that's not our problem but yours.
For the particular failures in your build, the issues look like a problem of musl linker. It seems that it requires all dependency of libraries to be used, even if an executable doesn't use a library directly.
If it is the case, we need a patch... something like:
Mar 24 2023
@gniibe
Trying to crosscompile newer 2.4 gpg toolstack from Heads OSF under PR https://github.com/osresearch/heads/pull/1350
FWIW, some cards don't have PUKs but two PINs which are able to unblock reciprocal.
Should we also differentiate between wrong PUK and no PUK set?
Having GPG_ERR_BAD_PUK makes sense. So, I added a tag for gpg-error.
Mar 23 2023
Fixed in master (of libgpg-error).
Pushed the change to libgcrypt (master and 1.10 branch).