Arch Linux User Repository

@tyreq I'm trying the fix rn. 3.7's site packages could be left because of use of pip install with sudo. Check if any package owns the files - also not updated python-* packages from AUR.

@yurikoles @MarcinWieczorek @MangoMan had the same problem. it seems that --with-ensurepip=upgrade (default) in ./configure/ Python tried to delete the previously intalled pip to reinstall it's bundled version (via pip itself) and failed, since it's lacking permissions in /usr/lib/python37/

Changing --with-ensurepip in PKGBUILD:79 to --with-ensurepip=install just keeps the already installed pip and goes on succesfully

Requirement already satisfied: pip in /usr/lib/python3.7/site-packages (19.0.3)

Some further thoughts: I've had arch's system python upgrade from 3.7 to 3.8, but it kept /usr/lib/python3.7/site-packages for some reason. Don't know if that is intended or not, but it resulted in this behaviour.

I have a similar issue like MarcinWieczorek

@dspati Cool. Thanks!

@MarcinWieczorek do you have something similar with other AUR packages? Because it seems to be a local issue.

I'm getting an error:

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Looking in links: /tmp/tmpl85ku1xr
Collecting setuptools
Collecting pip
Installing collected packages: setuptools, pip
  Found existing installation: pip 19.0.3
    Uninstalling pip-19.0.3:
ERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/usr/bin/pip'
Consider using the `--user` option or check the permissions.

I have fakeroot installed.

@Ivellios Please have a look at the comment by '5long' at 2019-11-15 15:05, a few pages down.

==> Verifying source file signatures with gpg... Python-3.7.6.tar.xz ... FAILED (unknown public key 2D347EA6AA65421D)

@yurikoles

Running tests in check() is to check for correctness. Running tests with ./configure --enable-optimizations is for, literally, optimizations. They are different things. It's impossible to move ./configure --enable-optimizations into check() without breaking the build.

@5long

why don't you use PKGBUILD check function for test? It's straightforward to then --nocheck