Build fails due to incorrect sha512sum.
==> Validating source files with sha512sums...
vispy-0.16.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
| Git Clone URL: | https://aur.archlinux.org/python-vispy.git (read-only, click to copy) |
|---|---|
| Package Base: | python-vispy |
| Description: | Interactive visualization in Python |
| Upstream URL: | https://vispy.org |
| Licenses: | BSD-3-Clause |
| Submitter: | incomplete |
| Maintainer: | carlosal1015 |
| Last Packager: | carlosal1015 |
| Votes: | 2 |
| Popularity: | 0.000000 |
| First Submitted: | 2019-08-10 09:41 (UTC) |
| Last Updated: | 2026-02-05 13:38 (UTC) |
Build fails due to incorrect sha512sum.
==> Validating source files with sha512sums...
vispy-0.16.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Build fails due to incorrect sha512sum.
==> Validating source files with sha512sums...
vispy-0.15.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
The correct sha512sum seems to be: ed842930acb8e1fb62e83cd1c555c690fd057ab53f451f014a76944c0f5fe513bafb5d459a171334127427264be7602fbd4a1bf472d5b23f5d7c1e257c4d8c9f
mesa-utils dep not needed.
Add the following function to PKGBUILD to fix the currently broken build:
prepare() {
cd "$srcdir/${_pkgname}-${pkgver}"
sed -e '/oldest-supported-numpy/d' -i pyproject.toml
}
I had to change pyproject.toml to not refer to "oldest-supported-numpy" but rather just "numpy". I think the former is a meta package but I don't understand how the resolution of that works. I did have a recent numpy installed but it would not satisfy "oldest-supported-numpy".
The pyproject.toml has these commented-out lines before setuptools_scm_git_archive:
# Use these when setuptools>=42 is more widely available
# "setuptools>=42",
# "setuptools_scm[toml]>=3.4",
"setuptools_scm_git_archive",
This means that the only reason they did not remove the "git_archive" variant is that they were concerned about very old distributions and their packaging, instead of letting the old distributions take care of that matter instead of upstream.
The current developer seems clueless about this requirements definition.
Please take care of the problem by uncommenting the those lines and removing the one with "git_archive".
Please modernize the build to use pyproject.toml instead of setup.py, and patch that file to remove setuptools_scm_git_archive as it is not actually needed and that module is deprecated in favor of setuptools_scm.
The sha256sum seems to be wrong, therefore the build of this fails. For me the sha256sum seems to be 37b91f39f6830891ea2d54e631fe5363f8c00bee6da25ffc8c3ef04f2297ef9c.
Thanks for maintaining! I suggest adding python-opengl as a dep (or optdep) for 3D texture support, as well as bumping to 0.9.4!
Pinned Comments