tl2020 pretest begin

[khzimmer at posteo.de]

The error must be in TLUtils.pm, this function fails:

sub mkdirhier {
   my ($tree,$mode) = @_;
   my $ret = 1;
   my $reterror;

   if (-d "$tree") {
     $ret = 1;
   } else {
     my $subdir = "";
     # win32 is special as usual: we need to separate //servername/ part
     # from the UNC path, since (! -d //servername/) tests true
     $subdir = $& if ( win32() && ($tree =~ s!^//[^/]+/!!) );

     @dirs = split (/[\/\\]/, $tree);
     for my $dir (@dirs) {
       $subdir .= "$dir/";
       if (! -d $subdir) {
         if (defined $mode) {
           if (! mkdir ($subdir, $mode)) {
             $ret = 0;
             $reterror = "mkdir($subdir,$mode) failed: $!";
             last;
           }
(...)

The error states:   mkdir(//(PC name)/) failed for tree   (...)
so
this must have erroneously found FALSE:   if (! -d $subdir)

$subdir was my PC name with slashes, a text without spaces, like 
//testpc02/

Could somebody look into that problem on Windows 10?
Many of my users are already using Win 10, so if the problem remains 
they will not be able to use TL 2020 with SPBuchsatz.


Am 04.03.2020 08:19 schrieb khzimmer at posteo.de:
> PS: My mail was incorrect, I had started the installation like this:
> 
> install-tl-windows.bat -repository https://www.texlive.info/tlpretest/
> 
> on Windows 10, as normal user, not as admin.
> 
> (Previous installation of a released texlive, also on Win 10, had run
> without such error, using the same user account, in 2018.)
> 
> 
> Am 04.03.2020 07:01 schrieb khzimmer at posteo.de:
>> Hi,
>> 
>> just wondering: Did somebody else test installing on Windows 10?
>> 
>> I forgot to mention, my test box runs on Win 10, so perhaps that's the
>> reason for the error?
>> 
>> I had started installation (as a user, not as admin) by
>> double-clicking the install exe file, and made no extra modifications
>> in the GUI.
>> 
>> Cheers
>> Karl-Heinz
>> 
>> Am 03.03.2020 14:12 schrieb khzimmer at posteo.de:
>>> Hi Karl,
>>> 
>>> just tried installing this test version of tl2020 (after uninstalling
>>> tl2018) in a windows machine here.
>>> 
>>> Installation ended with this output:
>>> 
>>> | mktexlsr: Done.
>>> | C:/Users/(user
>>> name)/texlife-2020-pretest/install-tl/install-tl-20200303/install-tl:
>>> mkdir(//(PC name)/) failed for tree \\(PC name)\profile$\(user
>>> name)\AppData\Roaming\Microsoft\Windows\Start Menu\Programs/TeX Live
>>> 2020: No such file or directory at C:/Users/(user
>>> name)/texlife-2020-pretest/install-tl/install-tl-20200303/tlpkg/TeXLive/TLUtils.pm
>>> line 928.
>>> 
>>> Is that a known error?
>>> 
>>> Also, I can start TeXworks, but when trying to run lualatex it does
>>> not succeed but it ends with this:
>>> 
>>> | Running the command C:\texlive\2020\bin\win32\fmtutil-user.exe
>>> | This is LuaTeX, Version 1.12.0 (TeX Live 2020/W32TeX)
>>> |  restricted system commands enabled.
>>> | I can't find the format file `lualatex.fmt'!
>>> 
>>> Cheers,
>>> Karl-Heinz
>>> 
>>> 
>>> Am 03.03.2020 03:09 schrieb Karl Berry:
>>>> I think the pretest area is populated with the first build for TL 
>>>> 2020.
>>>> See https://tug.org/texlive/pretest.html as usual for details of how 
>>>> to
>>>> install (unchanged from previous years), and the list of notable 
>>>> changes
>>>> that I've got so far. Additions or corrections to the news are 
>>>> greatly
>>>> appreciated.
>>>> 
>>>> I have not caught up with the CTAN releases over the past few days. 
>>>> I
>>>> expect all of those to be updated in the pretest over the next day 
>>>> or two.
>>>> 
>>>> The binaries for a few of the platforms (cygwin, armhf-linux,
>>>> i386-netbsd) have not yet been updated. I expect that to happen soon
>>>> also.  All others are current AFAIK.
>>>> 
>>>> BTW, as discussed in the LaTeX newsletters and other places, 
>>>> lualatex in
>>>> the pretest now invokes the luahbtex engine, as lualatex-dev did for 
>>>> the
>>>> last couple months in TL19.
>>>> 
>>>> Please try it if you can. Better to test now than wait for breakage 
>>>> in
>>>> the official release. We have no dedicated testers or QA department, 
>>>> so
>>>> it's all up to us collectively as volunteers.
>>>> 
>>>> Hope it flies,
>>>> Karl