Bug 2503874

Summary: erlang-ebloom: FTBFS in Fedora rawhide/f45
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: erlang-ebloomAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: lemenkov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: erlang-ebloom-2.1.0-23.fc45 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-07-29 15:28:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2433833    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2026-07-21 18:28:04 UTC 
erlang-ebloom failed to build from source in Fedora rawhide/f45

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
Please fix erlang-ebloom 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-ebloom will be orphaned. Before branching of Fedora 46,
erlang-ebloom 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-07-21 18:28:09 UTC 
Created attachment 2149765 [details]
build.log
Comment 2 Fedora Release Engineering 2026-07-21 18:28:15 UTC 
Created attachment 2149766 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2026-07-21 18:28:18 UTC 
Created attachment 2149767 [details]
state.log
Comment 4 Peter Lemenkov 2026-07-29 15:28:53 UTC 
Fixed in erlang-ebloom-2.1.0-23.fc45.

The FTBFS on s390x was caused by a broken serialization implementation in the C++ NIF. The original serializer.hpp used native byte order writes and had an off-by-one bug (buffer_ initialized to original_buffer_ + 1 leaving the first byte uninitialized), causing two identically constructed bloom filters to serialize to different binaries on big-endian s390x with newer GCC.

Replaced serializer.hpp with portable fixed-width big-endian read_*/write_* primitives (uint32_t, uint64_t, htobe64/be64toh). Also dropped erl_nif_compat.h (pre-R14B NIF API shims no longer needed) and fixed the serialize() signature to write directly into the caller-provided buffer without a redundant len out-parameter. Addresses the upstream TODO: "Make this format platform independent!"