Bug 2021910 - rust-sequoia-sq: FTBFS with OpenSSL 3.0.0
Summary: rust-sequoia-sq: FTBFS with OpenSSL 3.0.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-sequoia-sq
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL:
Whiteboard:
Depends On: 1990657
Blocks: OpenSSL3.0 F36FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-11-10 12:24 UTC by Sahana Prasad
Modified: 2021-12-10 16:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-10 16:50:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sahana Prasad 2021-11-10 12:24:03 UTC
This bug is used to track the readiness of rust-sequoia-sq  with OpenSSL 3.0.0.

Currently the build fails to build with OpenSSL 3.0.0 with the following logs
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=78020239

Kindly fix them to ensure this package builds with OpenSSL 3.0.0

You can treat the deprecated warnings not as errors if you want to continue to use deprecated functions, but it is encouraged to use the new APIs, and this migration could be done sooner than later.

To not treat deprecated warnings as errors, you may use
-Wno-error=deprecated-declarations

To port to new APIs, kindly refer to the OpenSSL upstream migration guide:
https://www.openssl.org/docs/manmaster/man7/migration_guide.html

Thank you

Comment 1 Fabio Valentini 2021-11-10 15:29:14 UTC
I *would like to* build this package, but I cannot due to a Rust compiler / LLVM toolchain issue.

Comment 2 Fedora Admin user for bugzilla script actions 2021-11-21 00:27:36 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Fabio Valentini 2021-12-10 16:50:12 UTC
Fixed in rawhide after working around the LLVM toolchain problem:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-501d0ff49c


Note You need to log in before you can comment on or make changes to this bug.