I'm updating OpenImageIO to the latest version and usually simple version bumps and rebuilds work just fine, so I was surprised when the build failed...
RPM build errors: error: File not found: /builddir/build/BUILDROOT/OpenImageIO-2.2.11.1-1.fc34.x86_64/usr/lib64/python3.9/site-packages/OpenImageIO.so
Which literally has been fine a month ago...
As it turns out the library name changed to:
/usr/lib64/python3.9/site-packages/ OpenImageIO.cpython-39-x86_64-linux-gnu.so
Am I just supposed to glob this in my spec file or is there a macro which will generate the correct output?
I'm venting and I know it's not safe, but I'm a$$uming that upstream didn't change anything causing this. What I need is predictability so I don't have to fix stupid stuff. I've got enough to do with failures related to the mass rebuild.
Thanks, Richard
On 02. 02. 21 14:35, Richard Shaw wrote:
I'm updating OpenImageIO to the latest version and usually simple version bumps and rebuilds work just fine, so I was surprised when the build failed...
RPM build errors: error: File not found: /builddir/build/BUILDROOT/OpenImageIO-2.2.11.1-1.fc34.x86_64/usr/lib64/python3.9/site-packages/OpenImageIO.so
Which literally has been fine a month ago...
As it turns out the library name changed to:
/usr/lib64/python3.9/site-packages/OpenImageIO.cpython-39-x86_64-linux-gnu.so http://OpenImageIO.cpython-39-x86_64-linux-gnu.so
Am I just supposed to glob this in my spec file or is there a macro which will generate the correct output?
$ rpm --eval '%{python3_ext_suffix}' .cpython-39-x86_64-linux-gnu.so
I'm venting and I know it's not safe, but I'm a$$uming that upstream didn't change anything causing this. What I need is predictability so I don't have to fix stupid stuff. I've got enough to do with failures related to the mass rebuild.
I don't know *what* has changed but it was not Python.
If you build the extension with Python native tooling (setuptools/distutils/etc.) you always get the more complex suffix.
It is usually cmake/autotools/etc. scripts that build the extension with the simpler .so suffix.
On 02. 02. 21 14:54, Miro Hrončok wrote:
I don't know *what* has changed but it was not Python.
I suspect it was this:
https://github.com/OpenImageIO/oiio/pull/2807
On Tue, Feb 2, 2021 at 7:54 AM Miro Hrončok mhroncok@redhat.com wrote:
On 02. 02. 21 14:35, Richard Shaw wrote:
I'm updating OpenImageIO to the latest version and usually simple
version bumps
and rebuilds work just fine, so I was surprised when the build failed...
RPM build errors: error: File not found:
/builddir/build/BUILDROOT/OpenImageIO-2.2.11.1-1.fc34.x86_64/usr/lib64/python3.9/site-packages/OpenImageIO.so
Which literally has been fine a month ago...
As it turns out the library name changed to:
/usr/lib64/python3.9/site-packages/
OpenImageIO.cpython-39-x86_64-linux-gnu.so
http://OpenImageIO.cpython-39-x86_64-linux-gnu.so
Am I just supposed to glob this in my spec file or is there a macro
which will
generate the correct output?
$ rpm --eval '%{python3_ext_suffix}' .cpython-39-x86_64-linux-gnu.so
It would be great to add that to the guidelines. If I had found it there I probably wouldn't have even bothered to start this thread :)
On Tue, Feb 2, 2021 at 8:01 AM Miro Hrončok mhroncok@redhat.com wrote:
On 02. 02. 21 14:54, Miro Hrončok wrote:
I don't know *what* has changed but it was not Python.
I suspect it was this:
Thanks, that's why I didn't want to assign blame without the possibility of exception :)
Thanks, Richard
On 02. 02. 21 22:20, Richard Shaw wrote:
> Am I just supposed to glob this in my spec file or is there a macro which will > generate the correct output? $ rpm --eval '%{python3_ext_suffix}' .cpython-39-x86_64-linux-gnu.so
It would be great to add that to the guidelines. If I had found it there I probably wouldn't have even bothered to start this thread :)
Here you go: https://pagure.io/packaging-committee/pull-request/1048
The macro is relatively new, thanks for the reminder.