Hi, Karel Gardas <[email protected]> writes: > Thanks for doing this. I guess this will make buildbots owners live a > lot easier. So we (owners) just need to make sure buildbot is run on > account with cabal install installed. That's good...
Yes, you need two things: - have "cabal" on your (buildbot's) $PATH - tell me you want these updates to happen automatically And of course, migrate your buildslave to the new buildmaster... I think we are actually ready to start doing that now, so if people send me their buildslave data -- name and password -- off list, I can start adding the slaves... Your Solaris slave is definitely eligible... As for OpenBSD , we should first try to figure a way to fix it first... it may make sense to try updating your python and/or buildbot installation, since it *could* be a buildbot bug in the first place. Also, it may be that a core is in fact dumped, but is removed during cleanup -- is there a way to tell openbsd to create core dumps in a fixed location, say /tmp? Yours, Petr. PS: I have added 2 more slaves, with 32bit and 64bit GHC 6.10.4 respectively. This makes for 4 linux builders, covering most of the usual configurations. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
