Thanks for the report, I have merged the pull request to fix this now.
I had several mixed reactions to this, and had to reflect a bit and some
of my (still unfinished) thoughts are:
On CI using latest gnulib
- My primary use of CI is to have confidence in the tarball I release,
thus it is imp
Collin Funk wrote:
> I would assume that this shouldn't happen since bootstrap.conf uses
> GNULIB_REVISION to specify a Gnulib commit to use.
The CI intentionally ignores GNULIB_REVISION or a gnulib submodule
and instead always uses the newest gnulib from its 'master' branch,
so that
- we detect
Bruno Haible writes:
> Today the inetutils CI failed:
>
> 1 out of 6 hunks FAILED -- saving rejects to file
> /tmp/glpycudi5nxa/top/README-release.rej
> /home/runner/work/ci-check/ci-check/gnulib/gnulib-tool.py: *** patch file
> top/README-release didn't apply cleanly
> /home/runner/work/ci-che
