On Thu, Apr 21, 2011 at 09:26:12AM -0600, Rob Savoye wrote: > On 04/20/11 11:24, Richard Wilbur wrote: > > > Had I not already upgraded to the version on getgnash.org, the error > > mentioned above would make it impossible to do so with the normal > > tools. Thus, in the past when the "Release" file expired, I have > > resorted to disabling the getgnash.org repository. Then I watch > > [gnash-dev] and intermittently manually check getgnash.org for a new > > release, at which point I re-enable the getgnash.org repository and > > upgrade. > > What happened is when buildbot got restarted, I stopped building > packages manually, as it's time consuming. I assumed buildbot would be > adding binary packages to the repositories, but this hasn't happened. > The x86_64 build slave isn't under buildbot anyway, as it's a chroot on > my laptop. I guess I should build new binary snapshots manually again, > as I've got more targets as chroots than buildbot is currently supporting.
Wouldn't it be enough to hook all your chroots as build slaves for it to happen automatically ? --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html _______________________________________________ Gnash-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnash-dev
