rust-piper failed to build from source in Fedora rawhide/f41 https://koji.fedoraproject.org/koji/taskinfo?taskID=120761783 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild Please fix rust-piper 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, rust-piper will be orphaned. Before branching of Fedora 42, rust-piper 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/
Created attachment 2042690 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 2042691 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 2042692 [details] state.log
The build failure was caused by a known issue - intermittent and non-deterministic test failures. The failures happened infrequently enough that I never had good logs to report things, but I now have two failures on x86_64 and aarch64 and filed an upstream issue: https://github.com/smol-rs/piper/issues/18 If this cannot be easily resolved, then rebuilding the package (a few times) or disabling tests temporarily should resolve the problem for now.
FEDORA-2024-825180b276 (rust-piper-0.2.4-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-825180b276
FEDORA-2024-825180b276 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-825180b276` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-825180b276 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-825180b276 (rust-piper-0.2.4-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.