Bug 2505460

Created attachment 2152203 [details]
build.log

Created attachment 2152204 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Created attachment 2152205 [details]
state.log

In https://bodhi.fedoraproject.org/updates/FEDORA-2026-2551d0d66b we have shipped Python 3.15.0b4.

All packages that link to libpython or have extension modules should be rebuilt, or they will segfault on import/usage.

Packages using stable ABI might not need a rebuild.

This package was not rebuilt because we were unable to do so.
Please rebuild it with Python 3.15.0b4+ ASAP. Thanks

Please respond.

Hello Pavel and Artyom, are you gonna handle this issue or do you want me to fix it?

https://src.fedoraproject.org/rpms/openvino/c/17fb18a46f6951adad4a3c1bfe5ebe03cd73cd0b?branch=rawhide

Hi, folks,

Yeah, thanks for checking this.

From my side, if it is possible, I would prefer to merge the NPU part first:
https://src.fedoraproject.org/rpms/openvino/pull-request/10

As I understand, Fedora is currently doing the rebuild with the newer Python version, and our package failed during this rebuild. 
So maybe the best option is to merge the NPU changes first and then let OpenVINO be rebuilt again as part of this process.

We have been trying to get the 2026.0 release merged for quite a long time already. During this time, 2026.1, 2026.2 and 2026.3 were released, and 2026.4 is coming soon. Taking this into account, I would prefer to avoid spending additional time on 2026.0 if we can move directly to the latest available OpenVINO version after the NPU part is merged.

One more problem from my side is that I cannot restart this rebuild myself, and I also do not see the actual error logs for the failed build. S
o at the moment I cannot check what exactly failed there.
If someone can help with the rebuild/logs from Fedora side, it would be very helpful.

See https://koschei.fedoraproject.org/package/openvino and look for build.log

-- Found Protobuf: /usr/lib64/libprotobuf.so (found suitable version "3.19.6", minimum required is "3.19.6")
CMake Error at /usr/lib64/cmake/ONNX/ONNXConfig.cmake:8 (find_package):
  Could not find a package configuration file provided by "Protobuf" with any
  of the following names:
    Protobuf.cps
    protobuf.cps
    ProtobufConfig.cmake
    protobuf-config.cmake
  Add the installation prefix of "Protobuf" to CMAKE_PREFIX_PATH or set
  "Protobuf_DIR" to a directory containing one of the above files.  If
  "Protobuf" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  thirdparty/dependencies.cmake:558 (find_package)
  CMakeLists.txt:189 (include)
-- Configuring incomplete, errors occurred!
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.CJPfzT (%build)



The logs are also attached to this bugzilla.

https://src.fedoraproject.org/rpms/openvino/pull-request/10 has the same issue.

> From my side, if it is possible, I would prefer to merge the NPU part first:
> https://src.fedoraproject.org/rpms/openvino/pull-request/10

How do you propose merging and testing new features if the stack doesn't build?

> As I understand, Fedora is currently doing the rebuild with the newer Python
> version, and our package failed during this rebuild. 

You can't just not deal with the new version of python or what ever happens to be causing the failure.

> We have been trying to get the 2026.0 release merged for quite a long time
> already. During this time, 2026.1, 2026.2 and 2026.3 were released, and
> 2026.4 is coming soon. Taking this into account, I would prefer to avoid
> spending additional time on 2026.0 if we can move directly to the latest
> available OpenVINO version after the NPU part is merged.

Moving to 2026.3+ without new feature enablement would be a fine if it solves the FTB problems. Then land the NPU bits on top of that?

> If someone can help with the rebuild/logs from Fedora side, it would be very
> helpful.

They're attached to this bugzilla. A 'fedpkg scratch-build' against rawhide will give you the builds logs against the latest Fedora bits.

Thanks, folks!

PR #11 already contains the required fix and has previously passed a Rawhide Copr build. 
I can't retrigger the current Packit scratch build myself because my request to join the Fedora packager group, submitted over three months ago, is still pending. 
Could someone with packager permissions please retrigger PR #11?

Since PR #10 still has an unresolved packaging issue, I suggest merging PR #11 now, 
rebuilding OpenVINO against the current Rawhide/F45 buildroot with Python 3.15.0b4 or newer, and rebasing the NPU changes afterward.

Hello everyone, 
PR #11 is solving the onnx issue and I merged it. Plus I found a bug in intel_gpu and added a patch to fix it, and triggered the build.

FEDORA-2026-bebdb8b072 (openvino-2026.0.0-15.fc46) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bebdb8b072

FEDORA-2026-bebdb8b072 (openvino-2026.0.0-15.fc46) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.

For Python 3.15.0b4+ we also need a rebuild in Fedora 45.

FEDORA-2026-cfea3e346a (openvino-2026.0.0-15.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-cfea3e346a

FEDORA-2026-cfea3e346a has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-cfea3e346a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-cfea3e346a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.