Created attachment 708466 [details] koji build log showing error Description of problem: While building systemtap for rawhide, the build fails due to publican Version-Release number of selected component (if applicable): Publican 3.0 How reproducible: always Steps to Reproduce: 1. fedpkg co systemtap 2. fedpkg build 3. Actual results Build failure pointing to: revnumber (2.0) does not match the required format of '^([0-9.]*)-([0-9.]*)$/' at /usr/bin/publican line 692. Expected results: The docbook builds as normal Additional info: The specific build where the error occurred: http://koji.fedoraproject.org/koji/taskinfo?taskID=5106950 build log attached
Created attachment 708508 [details] Second failed build.log with X error
After adding fixes for BZ642127, building systemtap now fails with the error, The switch --header-spacing, is not support using unpatched qt, and will be ignored.The switch --footer-spacing, is not support using unpatched qt, and will be ignored.The switch --header-html, is not support using unpatched qt, and will be ignored.wkhtmltopdf: cannot connect to X server wkhtmltopdf died, PDF generation failed. Check log for details. at /usr/bin/publican line 887. I've attached the second build.log with full output
This dependency on an X connection is breaking builds. Please fix.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This should be fixed in Publican 3.1.5-1 (currently in testing)
Is this still an issue for you in F19 builds?
I just ran a scratch build with_docs enabled, the dependency on X is still breaking the build Task: http://koji.fedoraproject.org/koji/taskinfo?taskID=5304831 I'll also upload the latest build.log for examination.
Created attachment 740441 [details] latest build.log with X failure
systemtap has started invoking publican under a xvfb-run wrapper, just to work around publican's odd run-time requirement to have an well-staffed X $DISPLAY. Even this is not robust. Please fix publican not to require a live X display just to format some text files.
Publican doesn't require an X display, if one of it's deps requires X then that dep has an error.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.