-
Notifications
You must be signed in to change notification settings - Fork 54
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
v1.9.0 tarball checksum changed #67
Comments
Hi @mabraham. Thanks for the report. It was a surprising to me as I don't recall that I did any rebuild. On a quick search it seems to be a problem with GitHub. I guess that the best bet is to download releases from PyPI. Those tarballs are uploaded from my machine and the PyPI prohibits multiple uploads of the same version tarball. |
Thanks for the info. Another possibility is revealed by macports buildbot - that it is getting the download from https://distfiles.macports.org/py-arpeggio (see https://paste.macports.org/0480d2201c5c), which might be a tarball originally from PyPI. The git history for the portfile notes the maintainers intent to use a tarball that has the tests, but perhaps that was not correctly implemented / documented. Only the buildbots of old MacOS versions are failing, however. Will explore more tomorrow. |
The tests have become part of the source tarball PyPI release since v1.9.1, so that might be the underlying reason. Please see here |
I went to PyPI to investigate, and found that from https://pypi.org/project/Arpeggio/1.9.2/#files the source code link gives a 40K file from https://files.pythonhosted.org/packages/0e/a0/1fe16e650729c121af617d2038608b60359454e93e652f152a5c69abadf8/Arpeggio-1.9.2.tar.gz, but the download link on the left https://github.com/textX/Arpeggio/archive/v1.9.2.tar.gz comes from textX on github and is 748K (presumably because it has tests). Is that a problem to fix? MacPorts downloads the small one in its testing, so I'll try to move forward and fix that there. The larger one has some additional regression tests, docs, examples, and perf tests. Any idea why that would be, @igordejanovic? |
@mabraham The large one is created by GitHub (probably on-the-fly) from the whole source tree. The small one is what I created when the release has been made. So the small one should be used. |
Reverted to using Arpeggio tarball from PyPi that now has tests (since 1.9.1). Previous version used the Arpeggio tarball on github, but had a checksum that was probably from the Arpeggio tarball on PyPI. See textX/Arpeggio#67 for discussion. Added missing dependency on pytest-runner Removed some redundant logic on testing.
The macports port of arpeggio v1.9.0 is currently broken because the checksums computed when the port was made (see https://github.com/macports/macports-ports/blob/master/python/py-arpeggio/Portfile) don't match those computed for the current download:
I downloaded it manually on two different systems and verified that the sha256sum matches that found by macports. So I conclude that the tarball was rebuilt somehow.
Please do not make "updates" to tarballs once computed, because downstream automation relies on them not changing. (Learned this myself once the hard way! :-))
I will submit a fix to macports
The text was updated successfully, but these errors were encountered: