-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
reproducibility issue sha256sum changed on 5.1 archive #133
Comments
I don't know. You might want to ask GitHub, as these archives are automatically generated by their software. |
I'm unable to locally produce (with |
Thank you for looking into that.
Then :
Here the differences: Comparing
|
The archives in PyPI aren't generated by |
Dear @Changaco,
thank you for this useful package.
I would like to ask you if you happen to know why the
https://github.com/Changaco/python-libarchive-c/archive/5.1.tar.gz
has different sha256sum from the one on August 20.
Here is the commit I made with the version that I got on that day or 1-2 days before:
https://codeberg.org/stagex/stagex/src/commit/266467f61bc62e8e67ce5a72309ba0d127d015af/packages/py-libarchive/Containerfile#L3
Thank you for your time!
PS: If it doesn't burden/bother you much, it would be super helpful for everybody using this package if you were pgp signing your git commits!
The text was updated successfully, but these errors were encountered: