Bug 2047043 - transactional-update: FTBFS in Fedora rawhide/f36
Summary: transactional-update: FTBFS in Fedora rawhide/f36
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: transactional-update
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F36FinalFreezeException F36FTBFS F37FTBFS
TreeView+ depends on / blocked
 
Reported: 2022-01-27 09:54 UTC by Fedora Release Engineering
Modified: 2022-04-19 22:03 UTC (History)
2 users (show)

Fixed In Version: transactional-update-3.6.2-3.fc37 transactional-update-3.6.2-3.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-19 22:03:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2022-01-27 09:54 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2022-01-27 09:54 UTC, Fedora Release Engineering
no flags Details
state.log (1.02 KB, text/plain)
2022-01-27 09:54 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2022-01-27 09:54:34 UTC
transactional-update failed to build from source in Fedora rawhide/f36

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix transactional-update 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,
transactional-update will be orphaned. Before branching of Fedora 37,
transactional-update 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-27 09:54:36 UTC
Created attachment 1856736 [details]
build.log

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

Comment 2 Fedora Release Engineering 2022-01-27 09:54:37 UTC
Created attachment 1856737 [details]
root.log

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

Comment 3 Fedora Release Engineering 2022-01-27 09:54:38 UTC
Created attachment 1856738 [details]
state.log

Comment 4 Ben Cotton 2022-02-08 20:32:39 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 2022-04-17 14:07:43 UTC
FEDORA-2022-a22decd98a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a22decd98a

Comment 6 Fedora Update System 2022-04-17 14:09:50 UTC
FEDORA-2022-192bbdb3cc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-192bbdb3cc

Comment 7 Fedora Update System 2022-04-17 14:10:00 UTC
FEDORA-2022-a22decd98a 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 Blocker Bugs Application 2022-04-17 14:11:01 UTC
Proposed as a Freeze Exception for 36-final by Fedora user ngompa using the blocker tracking app because:

 Fixes FTBFS for Fedora Linux 36

Comment 9 Fedora Update System 2022-04-17 15:44:30 UTC
FEDORA-2022-192bbdb3cc 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-192bbdb3cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-192bbdb3cc

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

Comment 10 Adam Williamson 2022-04-19 16:32:14 UTC
+6 in https://pagure.io/fedora-qa/blocker-review/issue/761 , marking accepted.

Comment 11 Fedora Update System 2022-04-19 22:03:55 UTC
FEDORA-2022-192bbdb3cc 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.