Bug 2364019 - cbmc: FTBFS in Fedora 42
Summary: cbmc: FTBFS in Fedora 42
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cbmc
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lukáš Zaoral
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-05 07:34 UTC by Lukáš Zaoral
Modified: 2025-05-14 02:29 UTC (History)
3 users (show)

Fixed In Version: cbmc-6.4.1-3.fc42
Clone Of:
Environment:
Last Closed: 2025-05-14 02:29:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Lukáš Zaoral 2025-05-05 07:34:41 UTC 
Description of problem:
Package cbmc fails to build from source in Fedora 42.

Version-Release number of selected component (if applicable):
6.4.1-1.fc42

Steps to Reproduce:
koji build --scratch f42 cbmc-6.4.1-1.fc42.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/cbmc

Reproducible: Always
Comment 1 Fedora Update System 2025-05-05 12:00:53 UTC 
FEDORA-2025-5e6e1babbc (cbmc-6.4.1-3.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e6e1babbc
Comment 2 Fedora Update System 2025-05-06 03:33:47 UTC 
FEDORA-2025-5e6e1babbc has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5e6e1babbc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e6e1babbc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-05-14 02:29:08 UTC 
FEDORA-2025-5e6e1babbc (cbmc-6.4.1-3.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.