Bug 2377046 - python-pyliblo3 fails to build with Cython 3.1.2
Summary: python-pyliblo3 fails to build with Cython 3.1.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyliblo3
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: MartinKG
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2365167
TreeView+ depends on / blocked
 
Reported: 2025-07-08 03:12 UTC by Charalampos Stratakis
Modified: 2025-08-05 07:07 UTC (History)
2 users (show)

Fixed In Version: python-pyliblo3-0.16.3-5.fc43
Clone Of:
Environment:
Last Closed: 2025-08-05 07:07:14 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Charalampos Stratakis 2025-07-08 03:12:50 UTC 
Hello,

We are planning to update Cython from 3.0.12 to 3.1.2 in Rawhide.

However python-pyliblo3 fails to build with the latest Cython version.

You can inspect the build failures at https://copr.fedorainfracloud.org/coprs/cstratak/Cython-3.1.2/package/python-pyliblo3/

Let us know here if you have any questions.

We'd appreciate help from the people who know this package best, but if you don't want
to work on this now, let us know so we can try to work around it on our side.
Comment 1 Charalampos Stratakis 2025-07-12 01:04:27 UTC 
Upstream Cython change relevant to the failures: https://github.com/cython/cython/pull/5830

Basically "long" should be replace by "int".
Comment 2 Charalampos Stratakis 2025-08-05 02:04:55 UTC 
PR: https://src.fedoraproject.org/rpms/python-pyliblo3/pull-request/1
Comment 3 Fedora Update System 2025-08-05 07:02:47 UTC 
FEDORA-2025-cb567cf784 (python-pyliblo3-0.16.3-5.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-cb567cf784
Comment 4 Fedora Update System 2025-08-05 07:07:14 UTC 
FEDORA-2025-cb567cf784 (python-pyliblo3-0.16.3-5.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.