Change octal encoding in header #414
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I had compatibility problems with tar files generated by the node-tar library.
In my case the archives were sent on proprietary embedded hardware, so it's quite specific.
On the other hand, the same archive generated with 7-zip or GNU tar worked perfectly. After observing the differences in the archives generated, it turned out that the significant difference was the way the numbers were encoded in the header.
This point has already been covered in ticket #28.
My pull request corrects my specific problem and outputs archives encoded in the manner of 7-zip and GNU tar.
Hope this can help