Re: [TCLCORE] Tcl/Tk 8.6.13 Release Candidates

[Donald P. <d.g...@co...>]

> On Nov 21, 2022, at 4:44 AM, Pietro Cerutti via Tcl-Core <tcl...@li...> wrote:
> 
> unixInit-3.2 fails: [encoding system] inside the spawned interpreter is iso8859-1. This gets fixed if I re-run the test after installation, so I guess somehow the test can't resolve the encoding files before they are installed. As a double check, I have renamed the installed encodings/ directory, re-run the test, and reproduced the failure.

I have just seen this test failing and opened a ticket about it, but when I see it fail, the failure is always associated with the encoding directory being in the zipfs, so I see the failure only when testing Tcl 8.7.

To be sure, you are seeing this failure from the 8.6.13 rc?  And not customizing it somehow to graft on any zipfs capability?

If that is right, can you take another moment to try the 8.6.12 release (one release older) and test for the same thing?  I want to see if some change in Tcl between releases is being seen, or whether some other cause is in play.

I will also try a build of RC3 where I use —exec-prefix to direct the install to unused filesystem space so prior installs of encoding files do not mask the issue.

I think I am willing to release 8.6.13 without a fix for this (only seems to cause problem pre-install, and only for systems not yet using utf-8 as a system encoding), but having more failure modes should speed the location of the issue.

DGP