When uncompressing a file with symlinks on 7-zip 19.00 on Windows, there were no errors presented. Granted, any symlinks that existed in the archive were uncompressed incorrectly.
Now after updating to 7-zip 22.01, I am getting errors about not being an admin:
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : .\llvm\clang
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : .\llvm\clang++
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : .\llvm\llvm-ranlib
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : .\llvm\llvm-strip
ERROR: Cannot create symbolic link : A required privilege is not held by the client. : .\llvm\wasm-ld
and the uncompress step fails with an error return code.
In our use case, we are uncompressing an artifact file on Windows that was shared for use on Windows, Linux and macOS, and did contain symlinks, but at the same time, these symlinks were never used on Windows, so for the purposes of our use case, 7-zip 19.00 behavior was alright.
Now after updating to 7-zip 22.01, we have an issue that it is no longer uncompressing this artifact file without errors, which is throwing off automated uncompression scripts.
It is great that 7-zip improved the symlink behavior on Windows, but at the same time, we find struggling with this improvement, and it's causing issues to our scenario.
I wonder if it would make 7-zip more robust if it had the following set of command line options:
These kinds of options would help users decide how to behave on different symlink scenarios.
Seems I also suffer from this problem:
STR with 7z version 23.01 on WIN 10:
» Expected: Unzips completely
Actual: Error Messages 😥