Bug 2550182

Summary:	simdjson: unannounced soname change
Product:	[Fedora] Fedora EPEL	Reporter:	Carl George 🤠 <carlwgeorge>
Component:	simdjson	Assignee:	Ali Erdinc Koroglu <ali.koroglu>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel10	CC:	ali.koroglu, orion
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-10-22 00:29:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Carl George 🤠 2026-10-13 03:38:43 UTC

Description of problem:
simdjson was updated from 3.12.3 to 5.0.1 in EPEL 10.3 and 10.4.  This new major version changes the library soname from libsimdjson.so.25 to libsimdjson.so.34.  This is breaking the installability of libmamba, which linked against the old soname.  There may also be third parties that built against this soname.  One of the following actions must be taken:

* revert this update with an epoch bump
* introduce a simdjson3 compat package
* rebuild libmamba against the new simdjson


Version-Release number of selected component (if applicable):
simdjson-5.0.1-1.el10_3
simdjson-5.0.1-1.el10_4


Additional info:
Aside from the soname change (which itself is bad enough), the upstream release notes describe this as a major update with major changes.  An update of this type is not allowed by EPEL policy.

https://docs.fedoraproject.org/en-US/epel/epel-policy/

If an update like this is unavoidable, then it must go through the incompatible updates policy.

https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/

Comment 1 Ali Erdinc Koroglu 2026-10-13 03:55:17 UTC

Hello Carl, I'll rebuild the libmamba with the new simdjson asap.
Sorry for the inconvenience, thank you.

Comment 2 Fedora Update System 2026-10-13 14:01:13 UTC

FEDORA-EPEL-2026-48aa6dabeb (libmamba-2.9.0-2.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-48aa6dabeb

Comment 3 Fedora Update System 2026-10-13 14:01:46 UTC

FEDORA-EPEL-2026-a5c594c98b (libmamba-2.9.0-2.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-a5c594c98b

Comment 4 Fedora Update System 2026-10-14 02:28:22 UTC

FEDORA-EPEL-2026-a5c594c98b has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-a5c594c98b

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

Comment 5 Fedora Update System 2026-10-14 02:35:02 UTC

FEDORA-EPEL-2026-48aa6dabeb has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-48aa6dabeb

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

Comment 6 Fedora Update System 2026-10-22 00:29:33 UTC

FEDORA-EPEL-2026-48aa6dabeb (libmamba-2.9.0-2.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-10-22 00:43:40 UTC

FEDORA-EPEL-2026-a5c594c98b (libmamba-2.9.0-2.el10_4) has been pushed to the Fedora EPEL 10.4 stable repository.
If problem still persists, please make note of it in this bug report.