I'm confirming this package will not build in a clean chroot.
Any chance something related to using an old AMD processor? I'm also not up to date on the host system, holding back on kernel, etc.
Git Clone URL: | https://aur.archlinux.org/python2.git (read-only, click to copy) |
---|---|
Package Base: | python2 |
Description: | A high-level scripting language |
Upstream URL: | https://www.python.org/ |
Licenses: | PSF-2.0 |
Conflicts: | python |
Submitter: | jelly |
Maintainer: | micwoj92 |
Last Packager: | micwoj92 |
Votes: | 76 |
Popularity: | 1.01 |
First Submitted: | 2022-09-23 10:01 (UTC) |
Last Updated: | 2024-06-17 22:01 (UTC) |
I'm confirming this package will not build in a clean chroot.
Any chance something related to using an old AMD processor? I'm also not up to date on the host system, holding back on kernel, etc.
I can confirm that running makepkg/yay with the recommended --nocheck option doesn't skip the tests (which eventually fail). One should probably edit the PKGBUILD file.
If your still getting the error try:
gpg --keyserver hkps://pgp.surf.nl --search-keys 04C367C218ADD4FF
this should provide a User-Id. And it is possible to import the key
I run with yay -S python2 --mflags "--nocheck", and test still not skip.
On some Arch derivative distro, rebuild-detector (checkrebuild -v) flag python2, to avoid this just install tk package (yay -S tk).
@xanadu73 pass --nocheck to makepkg to skip check(), it is in the first line of the pinned comment here
You can easily byass pgp problem by applying --skippgp option. However, I could not understand how to skip the tests being performed (because they fail). So, how should we modifly the pkg build file? Help appreciated.
Cause even removing check() altogether doesn't skip tests for me
Then you did it wrong
the makepkg option exists to skip test exist
oh no, I have already compiled it successfully, all tests pass here. I'm not asking for compilation help.
I'm trying to understand how this works. Cause even removing check() altogether doesn't skip tests for me
@eimis have you figured out to read the pinned comment before posting?
Pinned Comments