Change the test source location to support evolving downstream testing
requirements. This is needed both for downstream certification
activities and changes to test development for internal infrastructure
differences.
rpminspect reported:
A forbidden code point, 0x202E, was found in the pip-21.2.3/AUTHORS.txt source file on line 635 at column 0.
This issue was already found and fixed upstream
when pip was added to CentOS Stream for Python 3.11.
https://github.com/pypa/pip/pull/12046
However, the fix got overridden by upstream automation (which creates the file from git log).
The regression was reported upstream in https://github.com/pypa/pip/issues/12467
The patch still applies, so we could reuse it again.
However, rpminspect then not only does not stop reporting this,
but it starts reporting the same problem for the patch (from python3.12-pip):
A forbidden code point, 0x202E, was found in the 12046.patch source file on line 19 at column 11. This source file is used by (null).
A forbidden code point, 0x202E, was found in the 12046.patch source file on line 28 at column 1. This source file is used by (null).
A forbidden code point, 0x202E, was found in the pip-23.2.1/AUTHORS.txt source file on line 482 at column 10. This source file is used by python3.12-pip.spec.
A forbidden code point, 0x202E, was found in the pip-23.2.1/AUTHORS.txt source file on line 738 at column 0. This source file is used by python3.12-pip.spec.
The file is fine. It's not code.
Note that ideally, we would only exclude AUTHORS.txt, somehow like this:
unicode:
exclude: ^AUTHORS\.txt$
However, it does not work (at least on CentOS Zuul CI).
Cherry-picked from fd85d3c16a
(cherry picked from commit 2a64b8d1a3)
pip >= 20 has a mechanism that replaces our pip-allow-different-versions.patch
However, we kept our patch to support users doing e.g.:
$ pip install --user --upgrade 'pip<20'
However, pip 19.3.1 (the latest <20 version) does not even operate without distutils:
(venv3.12)$ pip list
Package Version
---------- -------
pip 22.3.1
setuptools 65.5.0
(venv3.12)$ pip install --upgrade 'pip<20'
...
(venv3.12) $ pip list
Traceback (most recent call last):
File ".../venv3.12/bin/pip", line 5, in <module>
from pip._internal.main import main
File ".../venv3.12/lib64/python3.12/site-packages/pip/_internal/main.py", line 13, in <module>
from pip._internal.cli.autocompletion import autocomplete
File ".../venv3.12/lib64/python3.12/site-packages/pip/_internal/cli/autocompletion.py", line 11, in <module>
from pip._internal.cli.main_parser import create_main_parser
File ".../venv3.12/lib64/python3.12/site-packages/pip/_internal/cli/main_parser.py", line 7, in <module>
from pip._internal.cli import cmdoptions
File ".../venv3.12/lib64/python3.12/site-packages/pip/_internal/cli/cmdoptions.py", line 19, in <module>
from distutils.util import strtobool
ModuleNotFoundError: No module named 'distutils'
Hence, it no longer makes any sense to keep the patch with Python 3.12.
It does no longer exist:
Usage: pipenv [OPTIONS] COMMAND [ARGS]...
Try 'pipenv -h' for help.
Error: No such option: --three (Possible options: --bare, --help, --where)
The `pipenv install` command will create the environment.
See https://src.fedoraproject.org/rpms/pipenv/c/5591b2df503495b
