On Tue, 20 Dec 2016 at 10:48, Branko Čibej <[email protected]> wrote:
> On 20.12.2016 10:05, Ivan Zhakov wrote: > > Hi, > > > > I've noticed that 'svn --version -v' displays wrong information about > > OS version on Windows 10 and later. > > > > For example: > > $ svn --version -v > > System information: > > > > * running on x86/x86_64-microsoft-windows6.2.9200 > > - Windows 10 Enterprise 2015 LTSB, build 10240 [6.3 Client > > Multiprocessor Free] > > * linked dependencies: > > - APR 1.5.1 (compiled with 1.5.2) > > - APR-Util 1.5.3 (compiled with 1.5.4) > > - Expat 2.2.0 (compiled with 2.2.0) > > - SQLite 3.11.1 (static) > > - Utf8proc 1.1.5 (compiled with 1.1.5) > > - ZLib 1.2.8 (compiled with 1.2.8) > > * loaded shared libraries: > > - C:\Ivan\SVN\trunk\Debug\subversion\svn\svn.exe (1.10) > > - C:\WINDOWS\SYSTEM32\ntdll.dll (6.2.10240.17184) > > - C:\WINDOWS\SYSTEM32\KERNEL32.DLL (6.2.10240.17113) > > - C:\WINDOWS\SYSTEM32\KERNELBASE.dll (6.2.10240.17184) > > [..] > > > > Notice that version is '6.2' while it should be 10.0. Version for OS > > modules are also wrong. This happens because svn.exe is not manifested > > properly and Windows enables 'version lie shims' in this case [1]. > > How about the "6.3 Client Multiprocessor Free" part? I suppose 6.3 is > correct in this case? AIUI that's the actual kernel version. > > Anyway ... looks good to me. We'll just have to remember to update the > manifest when the next version of Windows comes along, which is no worse > than macOS version mapping. > > -- Brane > > For the records, problem should be resolved in r1933257. -- Ivan Zhakov
