On Wed, Mar 09, 2022 at 07:44:29PM -0800, Mike Swanson wrote:
> I suspect it should be possible to catch this error from the Perl
> script and at least provide a warning that it was unable to create the
> non-UTF8 file name.
I made some change such that a test is skipped if it requires recoded
fil
On Wed, Mar 09, 2022 at 07:44:29PM -0800, Mike Swanson wrote:
> On Thu, 2022-03-10 at 04:35 +0100, Patrice Dumas wrote:
> > Now it is generated just before the tests in tp/tests. But won't the
> > issue be there too not at checkout time, but at make check time?
> > Could
> > you please test it?
>
On Thu, 2022-03-10 at 04:35 +0100, Patrice Dumas wrote:
> Now it is generated just before the tests in tp/tests. But won't the
> issue be there too not at checkout time, but at make check time?
> Could
> you please test it?
Yes it does fail with "make check":
make[4]: Entering directory '/home/
On Tue, Mar 08, 2022 at 02:39:53PM -0800, Mike Swanson wrote:
> I’m not sure for what purpose the file is in the repository, but it
> might be worth considering writing out non-UTF8 tests dynamically at
> build or runtime provided that the host operating system supports such
> names.
Now it is gen
On Tue, Mar 08, 2022 at 02:39:53PM -0800, Mike Swanson wrote:
> I know it’s not, strictly speaking, a bug, but it is common in ZFS
> installations to set utf8only=on to enforce that all file names are
> strictly UTF-8, and this causes an issue when trying to clone the Git
> repository for texinfo o
I know it’s not, strictly speaking, a bug, but it is common in ZFS
installations to set utf8only=on to enforce that all file names are
strictly UTF-8, and this causes an issue when trying to clone the Git
repository for texinfo on a ZFS system with that feature enabled:
$ git clone https://git.sav
