Bug 2045260 - clazy: FTBFS in Fedora rawhide/f36
Summary: clazy: FTBFS in Fedora rawhide/f36
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: clazy
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FTBFS F37FTBFS F38FTBFS
TreeView+ depends on / blocked
 
Reported: 2022-01-25 16:16 UTC by Fedora Release Engineering
Modified: 2023-01-29 02:29 UTC (History)
1 user (show)

Fixed In Version: clazy-1.11-1.fc37 clazy-1.11-1.fc36
Clone Of:
Environment:
Last Closed: 2023-01-29 01:31:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2022-01-25 16:16 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2022-01-25 16:16 UTC, Fedora Release Engineering
no flags Details
state.log (942 bytes, text/plain)
2022-01-25 16:16 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2022-01-25 16:16:03 UTC
clazy failed to build from source in Fedora rawhide/f36

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix clazy 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,
clazy will be orphaned. Before branching of Fedora 37,
clazy 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 Release Engineering 2022-01-25 16:16:07 UTC
Created attachment 1853812 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2022-01-25 16:16:09 UTC
Created attachment 1853813 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-01-25 16:16:11 UTC
Created attachment 1853814 [details]
state.log

Comment 4 Ben Cotton 2022-02-08 21:02:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Fedora Update System 2023-01-19 06:10:20 UTC
FEDORA-2023-4bffef7de9 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4bffef7de9

Comment 6 Fedora Update System 2023-01-19 06:10:21 UTC
FEDORA-2023-a1ec4ff2e1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a1ec4ff2e1

Comment 7 Fedora Update System 2023-01-21 03:31:00 UTC
FEDORA-2023-4bffef7de9 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-4bffef7de9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4bffef7de9

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

Comment 8 Fedora Update System 2023-01-21 16:28:22 UTC
FEDORA-2023-a1ec4ff2e1 has been pushed to the Fedora 36 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-a1ec4ff2e1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a1ec4ff2e1

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

Comment 9 Fedora Update System 2023-01-29 01:31:46 UTC
FEDORA-2023-4bffef7de9 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-01-29 02:29:52 UTC
FEDORA-2023-a1ec4ff2e1 has been pushed to the Fedora 36 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.