Bug 2045809 - libisds: FTBFS in Fedora rawhide/f36
Summary: libisds: FTBFS in Fedora rawhide/f36
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libisds
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FTBFS
TreeView+ depends on / blocked
 
Reported: 2022-01-25 18:36 UTC by Fedora Release Engineering
Modified: 2022-05-07 04:16 UTC (History)
1 user (show)

Fixed In Version: libisds-0.11.1-6.fc36 libisds-0.11.2-1.fc36
Clone Of:
Environment:
Last Closed: 2022-01-31 09:35:23 UTC
Type: ---
Embargoed:


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

Description Fedora Release Engineering 2022-01-25 18:36:22 UTC
libisds failed to build from source in Fedora rawhide/f36

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix libisds 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,
libisds will be orphaned. Before branching of Fedora 37,
libisds 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 18:36:24 UTC
Created attachment 1855251 [details]
build.log

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

Comment 2 Fedora Release Engineering 2022-01-25 18:36:26 UTC
Created attachment 1855252 [details]
root.log

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

Comment 3 Fedora Release Engineering 2022-01-25 18:36:27 UTC
Created attachment 1855253 [details]
state.log

Comment 4 Petr Pisar 2022-01-26 14:58:19 UTC
I know. GCC 12 reports use-after-frees at different places with different GCC versions. I will wait until GCC settles down because I verified one case yesterday and it looked more like a bug in GCC.

Comment 5 Petr Pisar 2022-01-31 09:35:23 UTC
I applied workarounds from upstream. The GCC 12 regression is handled in bug #2047715.

Comment 6 Fedora Update System 2022-03-30 12:21:59 UTC
FEDORA-2022-d11596483e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d11596483e

Comment 7 Fedora Update System 2022-03-31 18:24:50 UTC
FEDORA-2022-d11596483e 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 --advisory=FEDORA-2022-d11596483e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d11596483e

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

Comment 8 Fedora Update System 2022-04-05 12:41:00 UTC
FEDORA-2022-d6d4044ebc 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 --advisory=FEDORA-2022-d6d4044ebc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d6d4044ebc

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

Comment 9 Fedora Update System 2022-05-07 04:16:39 UTC
FEDORA-2022-d6d4044ebc 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.