Search Criteria
Package Details: python-google-crc32c 1.6.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-google-crc32c.git (read-only, click to copy) |
---|---|
Package Base: | python-google-crc32c |
Description: | Wraps Google's crc32c library into a Python wrapper |
Upstream URL: | https://github.com/googleapis/python-crc32c |
Licenses: | Apache-2.0 |
Submitter: | zhangkaizhao |
Maintainer: | a821 |
Last Packager: | a821 |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2020-09-24 09:27 (UTC) |
Last Updated: | 2024-09-03 17:53 (UTC) |
Dependencies (6)
- google-crc32cAUR
- python-setuptools
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-wheel (make)
- python-pytest (check)
Latest Comments
amstan commented on 2022-10-24 22:44 (UTC)
@Wupwup: If i were you I would just skip checks with
makepkg --nocheck
. Still no idea what triggers this failure (given that it uses the standard pip way to implementcheck()
), but it's something silly (you can run the tests manually frompkg/
and they'll work just fine) and does not represent the stability of the resulting package.Wupwup commented on 2022-10-22 15:46 (UTC)
This package is failing checks on my end and will not install
amstan commented on 2022-07-28 05:39 (UTC)
To close the loop. TLDR: Please ignore me, nothing to see here.
I guess this is just something that happens to most arch python packages on archlinuxarm.
I tried manually compiling pyalpm too (which is a normal binary package from the main repos). I took its PKGBUILD and ran it with makepkg (note that it's also got an x86 only
arch=()
, and it uses the same$CARCH
invocation in itscheck()
), and I got a similar error there.My conclusion (unverified) is that archlinuxarm packages are just compiled with --nocheck, otherwise you frequently get the error I described.
amstan commented on 2022-07-27 18:13 (UTC) (edited on 2022-07-27 18:14 (UTC) by amstan)
Aha!
For some context, I'm trying to run this on armv7.
Looks like the problem is that
$CARCH=armv7h
, whereas the python building names thingsarmv7l
.https://wiki.archlinux.org/title/Python_package_guidelines#:~:text=CARCH seems like the way to do it, but I'm wondering where the corner case is.
amstan commented on 2022-07-27 04:14 (UTC)
Is it just me or does the
check()
fail when it's being compiled in a clean setup.I think it works if the package is already installed (eg: at upgrade time).
Maybe line 26 is not very hermetic and tries to use the system libraries instead.