ncompress: update download sha #66305
Closed
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
This was failing to build from source soley because the sha256 was incorrect for the tarball. I don't have any direct knowledge of thie history of this package, but I suspect what happened is that the git history got rewritten per the comment here: vapier/ncompress#26 (comment) and that meant that github's generated tarball got changed slightly.
|
that is accurate. I renamed the old tags so the history is maintained, but the tarball for that specific tag is probably different since it points at a new commit history. the two should be identical if you unpack and compare. sorry for the trouble. |
|
The automatic PR checks failed because it doesn't like this type of change: hopefully a project admin can override somehow; I don't know the process |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This was failing to build from source soley because the sha256 was incorrect for the tarball.
I don't have any direct knowledge of thie history of this package, but I suspect what happened is that the git history got rewritten per the comment here: vapier/ncompress#26 (comment) and that meant that github's generated tarball got changed slightly.
@vapier can you confirm this hunch?