I have investigated more and can confirm the solution of @Rocky-IV. An existing (old) version of python2-pycparser leads to failing tests (and therefore failing build). My steps are:
sudo fakepkg python2-pycparser (to have the package if new build still fails)
sudo pacman -Rdd python2-pycparser
yay -S python2-pycparser
If I do so building and installing works.
Search Criteria
Package Details: python2-pycparser 2.21-1
| Git Clone URL: | https://aur.archlinux.org/python2-pycparser.git (read-only, click to copy) |
|---|---|
| Package Base: | python2-pycparser |
| Description: | C parser and AST generator written in Python |
| Upstream URL: | https://github.com/eliben/pycparser |
| Licenses: | BSD |
| Submitter: | bionade24 |
| Maintainer: | tallero (truocolo) |
| Last Packager: | truocolo |
| Votes: | 6 |
| Popularity: | 0.176906 |
| First Submitted: | 2022-01-08 16:10 (UTC) |
| Last Updated: | 2024-02-08 01:25 (UTC) |
df8oe commented on 2022-01-10 06:39 (UTC) (edited on 2022-01-10 06:41 (UTC) by df8oe)
Armag67 commented on 2022-01-09 20:50 (UTC)
Hello Rocky-IV,
I renamed the pycparser directory to old-pycparser in the /usr/lib/python2.7/site-packages/ directory and then python2-pycparser-2.21-1 build as a charm by the git clone way.
missingSleepDeps commented on 2022-01-09 20:42 (UTC)
@Rocky-IV solution works for me to. Far better than wasting a day reading up on what "clean chroot" even means, just to install a single package.
df8oe commented on 2022-01-09 17:17 (UTC)
I cannot build the package even in a clean chroot environment. And it is not yet in your inofficial repo...
Rocky-IV commented on 2022-01-08 23:56 (UTC)
Once I uninstalled existing python2-pycparser-2.20-3 from system builds fine! Remember to follow GitHub recommendations: 2.3 Known problems Some users who've installed a new version of pycparser over an existing version ran into a problem using the newly installed library. This has to do with parse tables staying around as .pyc files from the older version. If you see unexplained errors from pycparser after an upgrade, remove it (by deleting the pycparser directory in your Python's site-packages, or wherever you installed it) and install again.
alan1world commented on 2022-01-08 21:14 (UTC)
@alan1world You have to add the dependencies to the chroot with the -I flag. Look up the makechrootpkg manpage for more information.
@bionade24 Thank you but no.
I am aware of the -I flag. It's in the instructions under https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot. Which I followed.
This was how I ended up at the point of
ERROR: Could not resolve all dependencies.
bionade24 commented on 2022-01-08 20:34 (UTC) (edited on 2022-01-08 20:40 (UTC) by bionade24)
If building the package fails for you, either build in a clean chroot or disable the tests, but at your own risk that the functionality will be faulty.
This package builds fine in a clean chroot: https://abs-cd.oscloud.info/cd_manager/python2-pycparser
This package is also available in my unofficial user repo: https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud
bionade24 commented on 2022-01-08 20:31 (UTC)
@alan1world You have to add the dependencies to the chroot with the -I flag. Look up the makechrootpkg manpage for more information.
alan1world commented on 2022-01-08 19:47 (UTC)
Built in a clean chroot as per https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
Still fails.
==> ERROR: Could not resolve all dependencies.
==> ERROR: Build failed, check /home/user1/tmp/python2-pycparser/chroot/user1/build
Pinned Comments
bionade24 commented on 2022-01-08 20:34 (UTC) (edited on 2022-01-08 20:40 (UTC) by bionade24)
If building the package fails for you, either build in a clean chroot or disable the tests, but at your own risk that the functionality will be faulty.
This package builds fine in a clean chroot: https://abs-cd.oscloud.info/cd_manager/python2-pycparser
This package is also available in my unofficial user repo: https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud