python3-rpm ships two (slightly different) _rpm extension modules: $ repoquery -q --repo=rawhide -l python3-rpm | grep .so$ /usr/lib64/python3.11/site-packages/rpm/_rpm.cpython-311-x86_64-linux-gnu.so /usr/lib64/python3.11/site-packages/rpm/_rpm.so $ file /usr/lib64/python3.11/site-packages/rpm/_rpm.cpython-311-x86_64-linux-gnu.so /usr/lib64/python3.11/site-packages/rpm/_rpm.cpython-311-x86_64-linux-gnu.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=18a6d567fa41eeab9d3c3b6e2cce41bb5ef5e745, stripped $ file /usr/lib64/python3.11/site-packages/rpm/_rpm.so /usr/lib64/python3.11/site-packages/rpm/_rpm.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ca48b947b062a7c8aef8d80fb3279440ff1ab433, stripped When I run Python, I can only import one of them: >>> import rpm >>> rpm._rpm <module 'rpm._rpm' from '/usr/lib64/python3.11/site-packages/rpm/_rpm.cpython-311-x86_64-linux-gnu.so'> I suspect that _rpm.so is some autotools artefact while _rpm.cpython-311-x86_64-linux-gnu.so is from setup.py. I belive the _rpm.so file should be removed from the package for two reasons: 1) _rpm.cpython-311-x86_64-linux-gnu.so is the one that is being imported now, so removing the other one is "safer". 2) _rpm.cpython-311-x86_64-linux-gnu.so is a more standardized filename for a Python extension module. Version-Release number of selected component: 4.18.0-3.fc38
Ugh. Yeah, _rpm.so is indeed an autotools artifact. This must be an old, old thing. Thanks for spotting and reporting! (and the timing with the double lua-libs discovery is quite amusing)
Fixed in rpm-4.18.0-9.fc38