On Windows, directory symlinks and file symlinks are not the same.
If wrong type is used, the symlink just cannot be followed.
7z sometimes creates file symliks where directory symlinks should be.
In the following test case C:\User\t\lldb-7.0.1.src\packages\Python\lldbsuite\test is is a directory so C:\User\t\lldb-7.0.1.src\test\testcases must be SYMLINKD, not a SYMLINK
==================================
C:\User>curl --output lldb-7.0.1.src.tar.xz
https://releases.llvm.org/7.0.1/lldb-7.0.1.src.tar.xz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 18.4M 100 18.4M 0 0 18.4M 0 0:00:01 0:00:01 --:--:-- 12.0M
C:\User\t>7z x lldb-7.0.1.src.tar.xz -so | 7z x -aoa -si -ttar
7-Zip 18.05 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2018-04-30
Path =
Type = tar
Code Page = UTF-8
Everything is Ok
Folders: 1019
Files: 6728
Size: 86090754
Compressed: 4656128
C:\User\t>dir lldb-7.0.1.src\test
Volume in drive C has no label.
Volume Serial Number is 4484-BEB3
Directory of C:\User\t\lldb-7.0.1.src\test
12/15/2018 04:51 AM
C:\User\t>dir lldb-7.0.1.src\packages\Python\lldbsuite
Volume in drive C has no label.
Volume Serial Number is 4484-BEB3
Directory of C:\User\t\lldb-7.0.1.src\packages\Python\lldbsuite
12/15/2018 04:51 AM
On Windows, directory symlinks and file symlinks are not the same.
If wrong type is used, the symlink just cannot be followed.
7z sometimes creates file symliks where directory symlinks should be.
In the following test case C:\User\t\lldb-7.0.1.src\packages\Python\lldbsuite\test is is a directory so C:\User\t\lldb-7.0.1.src\test\testcases must be SYMLINKD, not a SYMLINK
Now it can be difficult to fix.
Maybe later.
Yes, this might require to track all created symlinks and after full unpack to check where do they point to, because the file or directory might be unpacked after the symlink and its type is not yet known at the time of symlink creation.
If you accept pull requests I can fix this bug
Maybe later.
@ipavlov this bug renders many orgs to be stuck on version 17x. There are so many great improvements in 18+, this bug is a really big problem for many orgs. Would you be willing to take this on this year?