[tahoe-dev] Compilation and using problems with tahoe 1.2.0 on many platforms ?

[Brian Warner]

> > - on debien etch, packages are broken, as many of the binary  
> > packages supplied as dependancies depends on a libc version from  
> > sid or ubuntu.
> 
> Could you tell me more about which ones are linked against an  
> incompatble?  I haven't seen this problem on our etch buildbot:
> 
> http://allmydata.org/buildbot/builders/etch

Our etch buildbot uses the regular tahoe build process, which
downloads+builds anything it needs. It doesn't use debian packages for this
purpose, so wouldn't expect it to notice the problem.

I did some tests from our etch buildslave, and it looks like the etch .debs
for python-pycryptopp and python-zfec are uninstallable because of libc
issues. The etch pycryptopp-0.5.2 .deb appears to be the same as the feisty
and sid versions. We have zfec-1.4.0 .debs for some platforms (feisty, gutsy,
hardy), but not for others (etch, edgy, sid have only zfec-1.1).

So Zooko, I think the task is to produce a pycryptopp .deb on our
'slave-etch' machine and replace the really-for-feisty one in our APT
repository. (you'll need to remove the .db file and rebuild the database,
unless you're also bumping the version number at the same time).


cheers,
 -Brian