Bug 2171465

Summary:	cryptopp: FTBFS in Fedora rawhide/f38
Product:	[Fedora] Fedora	Reporter:	Fedora Release Engineering <releng>
Component:	cryptopp	Assignee:	nucleo <alekcejk>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	alekcejk, aurelien, kwizart, vascom2
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cryptopp-8.8.0-1.fc37 cryptopp-8.8.0-1.el8 cryptopp-8.8.0-1.fc38	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-09 00:38:36 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:	2117176

Description Fedora Release Engineering 2023-02-20 11:46:10 UTC

cryptopp failed to build from source in Fedora rawhide/f38

https://koji.fedoraproject.org/koji/taskinfo?taskID=96319283


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
Please fix cryptopp at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
cryptopp will be orphaned. Before branching of Fedora 39,
cryptopp will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Update System 2023-06-30 10:39:29 UTC

FEDORA-2023-6ff72aa84b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ff72aa84b

Comment 2 Fedora Update System 2023-06-30 10:39:30 UTC

FEDORA-EPEL-2023-7e8bd2cec2 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7e8bd2cec2

Comment 3 Fedora Update System 2023-06-30 10:39:30 UTC

FEDORA-2023-f6bc9d1e49 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f6bc9d1e49

Comment 4 Fedora Update System 2023-07-01 01:33:05 UTC

FEDORA-2023-6ff72aa84b has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6ff72aa84b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ff72aa84b

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

Comment 5 Fedora Update System 2023-07-01 01:48:22 UTC

FEDORA-2023-f6bc9d1e49 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f6bc9d1e49`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f6bc9d1e49

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

Comment 6 Fedora Update System 2023-07-01 01:48:55 UTC

FEDORA-EPEL-2023-7e8bd2cec2 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7e8bd2cec2

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

Comment 7 Fedora Update System 2023-07-09 00:38:36 UTC

FEDORA-2023-6ff72aa84b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-07-09 00:45:06 UTC

FEDORA-EPEL-2023-7e8bd2cec2 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-07-09 02:18:18 UTC

FEDORA-2023-f6bc9d1e49 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.