-
Notifications
You must be signed in to change notification settings - Fork 37
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
fails to unpack a ghc bindist properly #49
Comments
It seems |
hasufell
added a commit
to hasufell/tar-bytestring
that referenced
this issue
Feb 21, 2020
hasufell
added a commit
to hasufell/tar-bytestring
that referenced
this issue
Feb 21, 2020
hasufell
added a commit
to hasufell/tar-bytestring
that referenced
this issue
Apr 1, 2021
hasufell
added a commit
to hasufell/tar-bytestring
that referenced
this issue
Apr 7, 2021
Bodigrim
pushed a commit
that referenced
this issue
Nov 15, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 15, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 15, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 17, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 17, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 18, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 19, 2023
Bodigrim
pushed a commit
that referenced
this issue
Nov 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unpacking a ghc bindist with tar is broken.
make
to fail, because various files are missing executable bitAnd indeed, searching for UncheckedShifts results in odd output (yes, the filename is truncated):
Searching a healthy unpacked dir (unpacked with cli tar) results in:
I couldn't reproduce it with a single overly long path. So I'm not sure this is a problem with path length. I suspect there is some really dangerous memory bug here.Edit: I could reproduce it with a single file: https://github.com/hasufell/tar-bug/releases/download/0.1.1/ghc-8.6.5.tar
The text was updated successfully, but these errors were encountered: