id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1326	don't require newer foolscap if you have older Twisted	zooko	davidsarah	"The current stable release—v1.8.1—[http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/_auto_deps.py?annotate=blame&rev=4799#L19 requires Twisted >= 2.4.0 and foolscap >= 0.5.1]. The current trunk [http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/_auto_deps.py?annotate=blame&rev=4893#L19 requires Twisted >= 2.4.0 and foolscap >= 0.6.0]. Brian [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-January/005842.html bemoaned] this increased requirement on the mailing list, since there is actually nothing wrong with {{{foolscap 0.5.1}}} ''unless'' you also happen to be using {{{Twisted >= 10.2}}}.

Brian gave as example that people on Ubuntu 10.04 Long-Term-Support ""Lucid"" have {{{Twisted-10.0}}} and {{{foolscap-0.5.1}}}.

This patch makes it so that if you already have {{{Twisted}}} installed and the version is {{{< 10.2}}} then the required version of {{{foolscap}}} is {{{>= 0.5.1}}}, else it is {{{>= 0.6.0}}}.

David-Sarah [http://tahoe-lafs.org/pipermail/tahoe-dev/2011-January/005867.html proposed] a different approach, in which {{{python setup.py build}}} would build a local private copy of {{{foolscap >= 0.6.0}}} even if the system already have {{{foolscap-0.5.1}}} installed. I'm not sure users would be okay with that behavior -- it runs counter to the desiderata that Tahoe-LAFS will use the packages that are provided in the system if they are of an acceptable version number.

In any case, I would like to apply my patch right away for Tahoe-LAFS v1.8.2, so {{{review-needed}}}!"	defect	closed	major	1.8.2	packaging	1.8.1	wontfix	setuptools install foolscap twisted