You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently discovered floj/minitar-lfn-problem illustrating an issue with minitar extraction of tarballs with very long filenames; it has never been reported as a bug. I have forked it as halostatue/minitar-lfn-problem and added an additional output because the diagnosis (missing files) is incorrect.
What is currently happening is worse because the files that are supposed to be missing are in fact mangled (that is, they are present, but they have been written to different locations than they should be). Comparing the extracted directories, we get this:
This was originally found with Minitar 0.9 but exists in Minitar 1.0.
The text was updated successfully, but these errors were encountered:
halostatue
changed the title
Minitar is altering some files with long file names on unpack
Minitar incorrectly roundtrips files with very long filenames
Aug 12, 2024
I recently discovered floj/minitar-lfn-problem illustrating an issue with minitar extraction of tarballs with very long filenames; it has never been reported as a bug. I have forked it as halostatue/minitar-lfn-problem and added an additional output because the diagnosis (missing files) is incorrect.
What is currently happening is worse because the files that are supposed to be missing are in fact mangled (that is, they are present, but they have been written to different locations than they should be). Comparing the extracted directories, we get this:
The most interesting part of that output is that the target directory structure is being duplicated:
We can see that the files are being written to a duplicate tree inside the tree:
This was originally found with Minitar 0.9 but exists in Minitar 1.0.
The text was updated successfully, but these errors were encountered: