fesco

#3596 OpenSSL 4.0 change reconsideration
Closed: Accepted by siosm. Opened by yselkowitz.

Closed: Accepted
Reopen Issue

The OpenSSL 4.0 change, while it went through the process, did not include any impact analysis. AFAICS no bugs or PRs were filed to prepare packages for the API changes in 4.0. Since merged yesterday in rawhide, it has quickly become apparent that dependents are not ready yet, and given its wide usage and low level in the dep tree, any breakage here can cause a lot of pain for package maintainers.

In short, it seems like this change is not fully baked, and given its nature being quite disruptive. Therefore, IMO it should at least be considered if it should be reverted, and the sooner we do that, the simpler that will be. If we could (very quickly!) get a mass-prebuild impact analysis to see exactly how widespread the damage is that would be best, but ultimately the decision is whether to revert the change immediately and require that a proper impact analysis be done, with bugs/PRs filed before getting reapproval from FESCo (which may also want to officially shepherd this change) to proceed.

(Sorry for the lack of detail, but wanted to get this in for today's meeting.)

Metadata Update from @ngompa:
- Issue tagged with: meeting

I'm attempting an analysis now at https://copr.fedorainfracloud.org/coprs/yselkowitz/openssl-4.0/monitor

I'm attempting an analysis now at https://copr.fedorainfracloud.org/coprs/yselkowitz/openssl-4.0/monitor

Not sure what data you expect from this rebuild, but in case a build succeeds, you should probably verify it happened with openssl 4 before considering it "good". E.g. python3.15, 3.14 and 3.13 will happen with openssl3-devel already.

FWIW, the same is true for any Rust packages with non-vendored dependencies. I already applied a "workaround" to build everything with openssl3 since the Rust bindings for OpenSSL don't support version 4 yet.

This was discussed in today's meeting: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-04-14/fesco.2026-04-14-17.01.html

The following was agreed (6,0,0):
1. Undo the change in Rawhide (untag openssl4, untag builds that link to openssl4)
2. Rebuild/re-tag missing packages
3. Add new provides to the openssl v3 packages
4. Create a COPR with openssl 4 and rebuild packages to get at least a buildroot & container image in a working state

FESCo appoints @yselkowitz and @sgallagh as Shepherds for the OpenSSL 4 Change to aid the maintainers in getting the packaging in order.

Sorry, I don't think it's a good idea

@dbelyavs let's be in touch regarding the next steps.

@yselkowitz I see. I left the comment before I've read the proposal.
I'm not happy to not been invited to FESCO discussion but sure, let's move forward.

Metadata Update from @siosm:
- Issue untagged with: meeting

Metadata Update from @siosm:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.