-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix long names (GNUTYPE_LONGNAME) #389
Conversation
To be clear, the issue is not related to long links. P.S. I did not submit this as a PR myself because it should probably not be part of |
Are you sure about that @RazerM? In my case, I am creating archives in exactly the same manner. The only difference is the length of the added paths. I had a look in my archiving library that I created a long time ago. It contains a specific |
The long links are stored in a header whose version bytes are "wrong", tar-rs does not look in invalid headers.
Using what? Sounds like it's creating out of spec headers. |
Apparently, I am using |
I mean what program or library are you using to create the archive |
See this library, the link references the specific line that is using the GNUTYPE_LONGNAME (L type header). |
I glossed over the link the first time because it's called |
Maybe you are right, this is not about longname. |
Thanks for waking me up. I have fixed the ustar version issue in my own library. Much appreciated. |
The patch suggested by @RazerM in #369 is fixing my problem of a truncated file name during extraction. In my case the long file names ended up in the root of the extraction directory rather than the sub-directory they have in the archive.
Is what @RazerM said last week. I'll be honest here: I don't have a clue at all. I'm just creating a PR for the solution that is solving my problem.