[tex-live] Lua module 'socket.url' loading problem with getmap

[Josef Kleber]

Hi,

I just received a bug report about getmap.sty
(https://bitbucket.org/kleberj/getmap/issues/2/error-argument-of-write-has-an-extra).

I get a different error message, but I can reproduce the problem with
fully updated TL2018.

\documentclass[12pt]{article}
\usepackage{graphics}
\usepackage{getmap}
\begin{filecontents*}{muc.epl}
&path=weight:5|color:orange|enc:okydHa}peAXOHi at jANv@A at kJJmFAiDJuAHmDXcBb@cC‘@gC^_DV}CJaCF{APaBVkBdAyEf at qC‘@{B\aDSwB
\end{filecontents*}
\begin{document}
\getmap[file=muc, mode=gm,
        markers={&markers=size:mid|label:H|color:green|München, Hbf
                 &markers=label:S|color:yellow|Stachus, München
				 &markers=label:M|color:blue|Marienplatz, München},
	    pathfile={muc.epl}]{}
\includegraphics[width=10cm]{muc}
\end{document}

leads to:

C:\texlive\2018\bin\win32\runscript.tlu:815:
c:/texlive/2018/texmf-dist/scripts/getmap/getmapdl.lua:13: module
'socket.url' not found:
        no field package.preload['socket.url']
        [kpse lua searcher] file not found: 'socket.url'
        [kpse C searcher] file not found: 'socket.url'
        no file 'C:\texlive\2018\bin\win32\socket.dll'
        no file 'C:\texlive\2018\bin\win32\loadall.dll'
        no file '.\socket.dll'
)
Runaway argument?
width=10cm]{muc} \end {document}
! File ended while scanning use of \Gin at iii.
<inserted text>
                \par
<*> bug_getmap_1

Relevant code in getmapdl.lua (/scripts/getmap)

local http = require("socket.http");
local ltn12 = require("ltn12")
local url = require("socket.url")

So I guess socket.http and ltn12 are found, but no socket.url!

The MWE was taken from getmap doc and created in 2016 with TL2016. The
latest questions on tex.sx are from early 2018, so I guess everything
was fine with TL2017. I got a new laptop a few weeks ago, so I have only
TL2018 available for testing. Maybe someone with an older version can
test the MWE?

I've read a few weeks ago that the handling of scripts were changed in
TL2018 (Win only??). Could this be the source of the problem? Any other
idea?

Thanks,

Josef