golang-googlecode-log4go failed to build from source in Fedora rawhide https://koji.fedoraproject.org/koji/taskinfo?taskID=28186001 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild Please fix golang-googlecode-log4go 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, golang-googlecode-log4go will be orphaned. Before branching of Fedora 30, golang-googlecode-log4go will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source
Created attachment 1462608 [details] build.log
Created attachment 1462609 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1462610 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
Been broken since F28 (bug 1555832); probably be retired (as it appear unneeded), because Google Code is dead.
golang-googlecode-log4go-0-0.13.hgc3294304d93f.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-94295cf33a
golang-googlecode-log4go-0-0.13.hgc3294304d93f.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-94295cf33a
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days