Bug 2333493

Summary:	python-meshio: FTBFS in Fedora Rawhide
Product:	[Fedora] Fedora	Reporter:	Sandro <gui1ty>
Component:	python-meshio	Assignee:	Sandro <gui1ty>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	42	CC:	gui1ty, neuro-sig, releng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
URL:	https://koschei.fedoraproject.org/package/python-meshio
Whiteboard:
Fixed In Version:	python-meshio-5.3.5-4.fc42	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-28 00:17:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2300528, 2332159

Description Sandro 2024-12-20 12:15:44 UTC

Description of problem:
Package python-meshio fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
5.3.5-1.fc42

Steps to Reproduce:
koji build --scratch f42 python-meshio-5.3.5-1.fc42.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/python-meshio

Reproducible: Always

Actual Results:  
Lots of tests are failing when run against NumPy 2.x.

Comment 1 Sandro 2025-01-22 22:31:27 UTC

*** Bug 2341169 has been marked as a duplicate of this bug. ***

Comment 2 Aoife Moloney 2025-02-26 13:20:26 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 3 Fedora Update System 2025-03-22 21:23:49 UTC

FEDORA-2025-419811941e (python-meshio-5.3.5-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-419811941e

Comment 4 Fedora Update System 2025-03-28 00:17:26 UTC

FEDORA-2025-419811941e (python-meshio-5.3.5-4.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.