icebreaker failed to build from source in Fedora rawhide/f34 https://koji.fedoraproject.org/koji/taskinfo?taskID=60910449 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild Please fix icebreaker 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, icebreaker will be orphaned. Before branching of Fedora 35, icebreaker 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 1753325 [details] build.log
Created attachment 1753326 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1753327 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 34. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29). A week before the mass branching of Fedora 35 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 33 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
I haven't looked deeply, but I suspect the problem here is that "level" has a restricted set of values in practice, but that the restrictions aren't visible at all in the source or at the point where we're doing the sprintf analysis. As a result the sprintf analysis bits make conservative assumptions and we get the diagnostic.
(In reply to Jeff Law from comment #7) That's right. The message error: ' (Easy)' directive output may be truncated writing 7 bytes into a region of size between 5 and 14 indicates that the analysis determined that truncation is possible but not inevitable. If the integer argument is guaranteed to be constrained to a range that makes truncation impossible then asserting that range just before the snprintf call should avoid the warning. But if the argument is not constrained then handling the truncation by testing the snprintf return value and taking some corrective action if it happens is the expected way to handle it.
The following builds were made after this report was opened: icebreaker-2.1.3-1.fc34
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days