Re: gnulib-tool.py current status

2024-04-11 Thread Bruno Haible
Collin Funk wrote:
> * Packages successfully tested with gnulib-tool.py
> 
>   bison
>   coreutils
>   cppi
>   cpio
>   diffutils
>   findutils
>   freedink
>   Update AC_PREREQ to 2.64 required.
>   gnutls
>   grep
>   groff
>   gzip
>   inetutils
>   libiconv
>   mailutils
>   patch
>   pspp
>   sed
>   tar
>   wget
>   wget2

And I have tested these with GNULIB_TOOL_IMPL=sh+py. (A few of these tests
may have been ineffective, for packages that insist to run gnulib-tool
from a particular gnulib revision. But I don't think this matters much.)

  acct
  barcode
  bison
  coreutils
  cpio
  CSSC
  cvs
  datamash
  dico
  diffutils
  findutils
  freedink
  gcal
  gettext REPORTED: creates an extra 'tests' directory
  gengetopt
  gmediaserver
  gnuit
  groff
  grub
  gsasl
  gsequencer
  gss
  grep
  guile
  gzip
  hello
  idutils
  inetutils
  jugtail REPORTED: missing --docbase not detected
  jwhois
  libffcall
  libiconv
  libidn
  libtasn1
  libtool
  libunistring
  licenseutils
  m4
  mailutils
  mini-httpd
  myserver
  nano
  octave
  parted
  patch
  pdf
  poke
  pspp
  radius
  recutils
  reindeer
  rcs
  sed
  shishi
  tar
  texinfo
  time
  vc-dwim
  wdiff
  wget
  wget2
  zile
  gawk

Bruno






Re: gnulib-tool.py current status

2024-04-10 Thread Bruno Haible
Hi Collin,

> By the way, here is a list of packages that I have tested using your
> method here:
> 
>  https://lists.gnu.org/archive/html/bug-gnulib/2024-04/msg00018.html

Good progress!

> These were done sometime in the past ~10 commits, so I would have to
> go through and double check no breakage occured since then.

This is not needed. For protecting against regressions, we have the test suite.
If the test suite shows no failures, it is unlikely that there are regressions
in the various packages.

> * Packages successfully tested with gnulib-tool.py
> 
>   bison
>   coreutils
>   cppi
>   cpio
>   diffutils
>   findutils
>   freedink
>   Update AC_PREREQ to 2.64 required.
>   gnutls
>   grep
>   groff
>   gzip
>   inetutils
>   libiconv
>   mailutils
>   patch
>   pspp
>   sed
>   tar
>   wget
>   wget2

Good; I'm testing some more of them.

> * Packages with issues with gnulib-tool.py
>   guile
>   /home/collin/.local/src/gnulib/gnulib-tool.sh: *** patch file 
> gnulib-local/m4/clock_time.m4.diff didn't apply cleanly
>   /home/collin/.local/src/gnulib/gnulib-tool.sh: *** Stop.

This only means that this .diff file is out-of-date. I would just remove
it and continue:
  $ git rm gnulib-local/m4/clock_time.m4.diff
  $ git commit gnulib-local/m4/clock_time.m4.diff
  $ ./autogen.sh

>   rcs
>   /home/collin/.local/src/gnulib/gnulib-tool.sh: *** file 
> /home/collin/.local/src/gnulib/build-aux/missing not found
>   /home/collin/.local/src/gnulib/gnulib-tool.sh: *** Stop.

This is a problem with the Automake version of invocation; gnulib-tool
does not do anything w.r.t. build-aux/missing. You can ignore it.

Bruno