[tahoe-dev] buildbot status -- Ruben Fedora (was: let's release what we've got (was: plans for tahoe-1.4.0))

Zooko O'Whielacronx zooko at zooko.com
Thu Apr 23 20:17:40 UTC 2009


Since one of my main goals for the tahoe-1.5 release (excpected in  
June) is to make Tahoe suitable for inclusion in Debian and Fedora,  
I'm looking again at Ruben's Fedora buildbot:


We demoted it from Supported to Unsupported status before the  
tahoe-1.4 release [1], and I'd like to get it back into Supported for  
the 1.5 release.  And not at the last minute, either -- I like for  
Supported buildbots to show some stability over the long term.  (For  
example, Dan's ArchLinux buildbot continues to languish in the  
Unsupported category because we haven't yet *quite* figured out what  
made it start working again, but we're getting close.)

My guess is that Ruben changed the installation of pycryptopp on his  
buildbot.  Maybe he was experimenting with the --disable-embedded- 
cryptopp flag or something?  That would be great, because getting it  
to work with that flag is my next goal.

Ruben: do you know what changed on your Fedora buildbot?



[1] http://allmydata.org/pipermail/tahoe-dev/2009-April/001592.html

More information about the tahoe-dev mailing list