Bug 2434022 - erlang-riak_dt: FTBFS in Fedora rawhide/f44
Summary: erlang-riak_dt: FTBFS in Fedora rawhide/f44
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang-riak_dt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F44FTBFS
TreeView+ depends on / blocked
 
Reported: 2026-01-28 17:35 UTC by Fedora Release Engineering
Modified: 2026-02-20 01:17 UTC (History)
1 user (show)

Fixed In Version: erlang-riak_dt-3.0.0-7.fc43 erlang-riak_dt-3.0.0-7.fc42
Clone Of:
Environment:
Last Closed: 2026-02-20 00:53:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (14.72 KB, text/plain)
2026-01-28 17:35 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2026-01-28 17:35 UTC, Fedora Release Engineering
no flags Details
state.log (1.67 KB, text/plain)
2026-01-28 17:35 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2026-01-28 17:35:08 UTC
erlang-riak_dt failed to build from source in Fedora rawhide/f44

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
Please fix erlang-riak_dt 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,
erlang-riak_dt will be orphaned. Before branching of Fedora 45,
erlang-riak_dt 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 2026-01-28 17:35:14 UTC
Created attachment 2124403 [details]
build.log

Comment 2 Fedora Release Engineering 2026-01-28 17:35:21 UTC
Created attachment 2124404 [details]
root.log

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

Comment 3 Fedora Release Engineering 2026-01-28 17:35:25 UTC
Created attachment 2124405 [details]
state.log

Comment 4 Fedora Update System 2026-02-11 19:40:33 UTC
FEDORA-2026-140f7d05c3 (erlang-riak_dt-3.0.0-7.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-140f7d05c3

Comment 5 Fedora Update System 2026-02-11 19:40:43 UTC
FEDORA-2026-2506bed361 (erlang-riak_dt-3.0.0-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2506bed361

Comment 6 Fedora Update System 2026-02-12 01:33:07 UTC
FEDORA-2026-2506bed361 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2506bed361`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2506bed361

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

Comment 7 Fedora Update System 2026-02-12 01:55:11 UTC
FEDORA-2026-140f7d05c3 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-2026-140f7d05c3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-140f7d05c3

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

Comment 8 Fedora Update System 2026-02-20 00:53:11 UTC
FEDORA-2026-2506bed361 (erlang-riak_dt-3.0.0-7.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-02-20 01:17:22 UTC
FEDORA-2026-140f7d05c3 (erlang-riak_dt-3.0.0-7.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.