What were you trying to do that didn't work?

I am trying to run rpmlint on packages with Python 3.8, 3.9 or 3.11 bytecode. It produces bogus error messages.

This is https://github.com/rpm-software-management/rpmlint/issues/128

The fix is https://github.com/rpm-software-management/rpmlint/commit/e52dcc73bab5c4310e9bb773e6aedea020e340ff

I fixed this upstream in rpmlint 1.11.

We are using rpmlint on our CI / gating and this breaks our test.

Please provide the package NVR for which bug is seen:

rpmlint-1.10-14.el8.noarch

How reproducible

Always

Steps to reproduce

1. yum install rpmlint python3.11-six
2. rpmlint python3.11-six
3. rpmlint python39-six
4. rpmlint python38-six
5. rpmlint python3-six

Expected results

python-bytecode-inconsistent-mtime should not be there, the mtime *is* consistent.

Actual results

python3.11-six.noarch: E: python-bytecode-inconsistent-mtime /usr/lib/python3.11/site-packages/_pycache_/six.cpython-311.pyc 1970-01-01T01:00:00 /usr/lib/python3.11/site-packages/six.py 2023-02-01T04:09:06
python39-six.noarch: E: python-bytecode-inconsistent-mtime /usr/lib/python3.9/site-packages/_pycache_/six.cpython-39.opt-1.pyc 1970-01-01T01:00:00 /usr/lib/python3.9/site-packages/six.py 2023-08-10T20:16:04
python39-six.noarch: E: python-bytecode-inconsistent-mtime /usr/lib/python3.9/site-packages/_pycache_/six.cpython-39.pyc 1970-01-01T01:00:00 /usr/lib/python3.9/site-packages/six.py 2023-08-10T20:16:04
python38-six.noarch: E: python-bytecode-inconsistent-mtime /usr/lib/python3.8/site-packages/_pycache_/six.cpython-38.opt-1.pyc 1970-01-01T01:00:00 /usr/lib/python3.8/site-packages/six.py 2023-08-06T05:37:35
python38-six.noarch: E: python-bytecode-inconsistent-mtime /usr/lib/python3.8/site-packages/_pycache_/six.cpython-38.pyc 1970-01-01T01:00:00 /usr/lib/python3.8/site-packages/six.py 2023-08-06T05:37:35