Bug 2396709 - libarrow: Please rebuild in Fedora 43
Summary: libarrow: Please rebuild in Fedora 43
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libarrow
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: PYC3.14rc3
TreeView+ depends on / blocked
 
Reported: 2025-09-19 13:31 UTC by Karolina Surma
Modified: 2025-10-03 00:16 UTC (History)
4 users (show)

Fixed In Version: libarrow-20.0.0-9.fc43
Clone Of:
Environment:
Last Closed: 2025-10-03 00:16:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2025-09-19 13:31:35 UTC
Dear package maintainer,

Due to reasons described in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/O6LBYY446Q2FWVBEVJCOJ34ADXTEIH65/ a rebuild of libarrow is needed in Fedora 43.

During the mass rebuild, it was determined that rawhide and f43 branches differ, hence I did not know if I could safely merge rawhide into f43 or if the f43 branch needs a diverging bump.

Please, determine this yourself and rebuild the package in Fedora 43, ideally before the Fedora 43 Final freeze (2025-10-07).

Thank you. Let me know if you need help.

Comment 1 Kaleb KEITHLEY 2025-09-19 14:31:56 UTC
No. libarrow-20 is in f43. I waited until after the branching to update rawhide to libarrow-21.

This was announced in the -devel mailing list. See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/U6Y257576LUWKXKYVKFNUCXZSWPN32Q5/

Comment 2 Miro Hrončok 2025-09-19 14:36:10 UTC
Please rebuild libarrow 20 in Fedora 43 to get the new Python bytecode then.

Comment 3 Ben Beasley 2025-09-22 13:45:25 UTC
The libarrow package is involved in https://bodhi.fedoraproject.org/updates/FEDORA-2025-5aa2157aca, which includes an abseil-cpp SONAME version bump and is critpath with 9 days remaining to stable-by-time. Editing that update at this point would risk missing Final Freeze.

Testing and karma on the update now in testing would be appreciated so that it can reach stable faster. Then we can follow up with a separate, standalone libarrow update to deal with Python 3.14.0rc3 bytecode.

Comment 4 Fedora Update System 2025-09-22 15:04:12 UTC
FEDORA-2025-2c6ca2cb99 (libarrow-20.0.0-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-2c6ca2cb99

Comment 5 Fedora Update System 2025-09-23 01:45:15 UTC
FEDORA-2025-2c6ca2cb99 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2c6ca2cb99`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2c6ca2cb99

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

Comment 6 Fedora Update System 2025-09-23 17:03:07 UTC
FEDORA-2025-4f84f3b4be (libarrow-20.0.0-8.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4f84f3b4be

Comment 7 Fedora Update System 2025-09-24 06:34:01 UTC
FEDORA-2025-389555c9ce (libarrow-20.0.0-9.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-389555c9ce

Comment 8 Fedora Update System 2025-09-25 01:38:47 UTC
FEDORA-2025-389555c9ce has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-389555c9ce`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-389555c9ce

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

Comment 9 Fedora Update System 2025-10-03 00:16:03 UTC
FEDORA-2025-389555c9ce (libarrow-20.0.0-9.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.