RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

To me it looks like the failure comes from the vendored openssl-sys crate. The rust package had a similar problem, maybe you can use the changes from there.

> To me it looks like the failure comes from the vendored openssl-sys crate. The rust package had a similar problem, maybe you can use the changes from there.

xref https://bugzilla.redhat.com/show_bug.cgi?id=1948976

Chasing a bunch of links here, it looks like there was a small patch here which implies the latest openssl crate supports this:
https://gitlab.com/redhat/centos-stream/rpms/rust/-/blob/c9s/rust-openssl-300.patch
Yet the PR in https://github.com/sfackler/rust-openssl/pull/1264 isn't merged?

For the rust package, I added a new Source which is a git snapshot of that pr1264, and then in %prep I'm replacing vendor/openssl*/ with it.

The Cargo.lock version patch is needed because that pr is based on the master version, which is already ahead of what was vendored. You might be able to just remove the lock file to let it regenerate during the build, but I knew that wouldn't work well with Rust's own bootstrap build process.

There's also the pesky .cargo-checksum.json in each vendored crate, which rust.spec is already hacking to clear its file list. Note that my Cargo.lock patch did *not* change the crate checksum, which needs to match that json value.

It's all very hacky, but... it's temporary.