Extract from tar fails. Most likely because path is too long

[Flarna]

Steps to reproduce (using TC 9.12 64Bit):
- Download NodeJs 9.2.0 source (https://nodejs.org/dist/v9.2.0/node-v9.2.0.tar.gz)
- Extract tar archive from gzip (works fine)
- Extract all files from tar into some folder, keep folder structure

Expected: Extract of all files works
Actual: Extract fails.

If I extract the same archive using 7-zip it works fine (and is also faster ).

I assume the reason is that the path of some file in the tar is too long for standard windows APIs (e.a. prefix "\\?\" needed).

[Dalai]

Confirmed, also that it's related to long path names. This is broken since at least 9.0 beta4. TC8 warns about the long files and asks whether to keep them. Newer versions just show an error "Access denied on target file" with the options Skip, Retry, Cancel and Rename.

I only tested TC 32 bit, but I guess it's the same in TC 64 bit.

Regards
Dalai

[petermad]

This is where TC fails the first time:
node-v9.2.0\deps\npm\node_modules\update-notifier\node_modules\latest-version\node_modules\package-json\node_modules\registry-url\node_modules\rc\node_modules\

which is only read as node-v9.2.0\deps\npm\node_modules\update-notifier\node_modules\latest-version\node_modules\package-json\node_modules\registry-url\node_modules\rc\node_modu

But that is only 156 characters long which is below Windows 259 charaters limit.

If I configure TC to use Total7zip for .tar files (tar=196,%COMMANDER_PATH%\PLUGINS\wcx\Total7zip\Total7zip.wcx) I can unpack the sample file.

[Flarna]

Ok, so seems to be more an issue in combining [face=courier]Filename prefix[/face] and [face=courier]File name[/face] fields of tar header which is cut off at 156 chars instead of allowing 255 chars.

[Dalai]

The archive itself can be extracted just fine when the destination is something like D:\node, but only in TC 9.x 32 bit. However, when the destination is D:\node\node\node\node\node\node\node\node\node\node TC 32 bit fails to do so with the error I mentioned above.

Conclusion: There are two different bugs/errors, one in TC 32 bit and another one in TC 64 bit.

Regards
Dalai

[petermad]

Here unpacking to G:\ fails at the same level in both TC 9.12 32bit and 64bit - the unpacking stops after 8.903 / 15.567 files (99,9 M / 141,8 M) 70% with the same error message:

"Access denied on file"
G:\node-v9.2.0\deps\npm\..\registry-...\node_modules\rc\node_modul

Interestingly the file count when unpacking with internal tar- unpacker and with Total7zip plugin is the same: 15.567 - so apparantly the internal tar unpacker can read all the file entries.

[ghisler(Author)]

I will check it, thanks.

[ghisler(Author)]

This should be fixed in TC 9.20 beta 1, please test it!

[Dalai]

Confirm the bugfix for TC 9.20 beta1 (32 bit); didn't test TC 64 bit. TC 9.20 beta1 behaves the same as TC 8.52a and warns about long paths asking whether or not to keep them.

Regards
Dalai

[Flarna]

Tested 64Bit variant of 9.20b1 and it looks good.

Thanks!