Description of problem: The sample buildbot setup (https://docs.buildbot.net/current/tutorial/firstrun.html) fails with "could not find buildbot-www; is it installed?" Version-Release number of selected component (if applicable): 1.1.0 How reproducible: $ sudo dnf install buildbot $ # From https://docs.buildbot.net/current/tutorial/firstrun.html : $ buildbot create-master master $ mv master/master.cfg.sample master/master.cfg $ buildbot start master Actual results: $ buildbot start master Following twistd.log until startup finished.. The buildmaster startup failed. Please see 'twistd.log' for possible reason. From twistd.log: [-] while starting BuildMaster Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1241, in gotResult _inlineCallbacks(r, g, deferred) File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1185, in _inlineCallbacks result = g.send(result) File "/usr/lib/python2.7/site-packages/buildbot/util/service.py", line 54, in reconfigServiceWithBuildbotConfig yield svc.reconfigServiceWithBuildbotConfig(new_config) File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1331, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) --- <exception caught here> --- File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 1185, in _inlineCallbacks result = g.send(result) File "/usr/lib/python2.7/site-packages/buildbot/www/service.py", line 211, in reconfigServiceWithBuildbotConfig self.setupSite(new_config) File "/usr/lib/python2.7/site-packages/buildbot/www/service.py", line 286, in setupSite raise RuntimeError("could not find buildbot-www; is it installed?") exceptions.RuntimeError: could not find buildbot-www; is it installed?
I've encountered this issue too. It makes it impossible to create a working build master configuration on fedora without restoring to pip to get buildbot-www installed.
> # minimalistic config to activate new web UI > c['www'] = dict(port=8010, > plugins=dict(waterfall_view={}, console_view={}, grid_view={})) try removing this from config. Unfortunately we don't have buildbot-www packaged (yet) due to some of its parts are written in nodejs which is problematic ;)
(In reply to Igor Gnatenko from comment #2) > due to some of its parts are written in nodejs which is problematic ;) Why is it problematic, given that Node.js and a huge swathe of related packages are in the repos? Genuinely curious.
Igor, does this mean that buildbot as currently packaged in Fedora 28 and Fedora 29 doesn't provide any web interface? Because the old web UI seems to be unavailable.
(In reply to Kamil Páral from comment #4) > Igor, does this mean that buildbot as currently packaged in Fedora 28 and > Fedora 29 doesn't provide any web interface? Because the old web UI seems to > be unavailable. Basicalyl yes.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
This was fixed quite a long time ago in F28...