A tool for installing and managing Python packages
e1694ed0fe
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
|
||
|---|---|---|
| tests | ||
| .gitignore | ||
| changelog | ||
| cve-2007-4559-tarfile.patch | ||
| dummy-certifi.patch | ||
| gating.yaml | ||
| no-version-warning.patch | ||
| nowarn-pip._internal.main.patch | ||
| python-pip.rpmlintrc | ||
| python-pip.spec | ||
| remove-existing-dist-only-if-path-conflicts.patch | ||
| rpminspect.yaml | ||
| sources | ||