On Sun, Oct 27, 2024 at 11:32:18PM +0100, Bruno Haible via Bug reports for the GNU Texinfo documentation system wrote: > Gavin Smith wrote: > > This appears to be a similar error to > > that which you reported earlier for Solaris 11 OmniOS for an earlier > > version of the code, Texinfo pretest 7.1.0.90, with an extra "0" file > > being created: > > > > https://lists.gnu.org/archive/html/bug-texinfo/2024-06/msg00027.html > > https://lists.gnu.org/archive/html/bug-texinfo/2024-06/msg00028.html > > https://lists.gnu.org/archive/html/bug-texinfo/2024-06/msg00044.html > > Oh, right. I had written that I reproduced it locally and that it was > a /bin/sh bug [1]. > > This time, I can't reproduce it locally (with or without > CONFIG_SHELL=/bin/bash). I would propose: > - either the workaround/fix that Patrice had proposed [2],
I remember that Gavin was opposed. I still think that having a way to customize the shell could be relevant independentely of this issue, but I'll let Gavin decide. > - or to drop Solaris 11 OmniOS from the CI. (We still have Solaris 11.4 > running.) And there is also the opencsw build farm CI, which is, in my opinion, even more interesting as it tests older setups than the Solaris 11.4 in the CI: https://buildfarm.opencsw.org/buildbot/waterfall?category=texinfo If we drop omnios from the platforms that are run, I think that it would be better to leave it in the file and retest from time to time. -- Pat