Le 20/09/2010 17:19, Adam GROSZER a écrit :
Hello Christophe,
Monday, September 20, 2010, 4:53:16 PM, you wrote:
CC> Le 19/09/2010 15:45, Marius Gedminas a écrit :
On Sun, Sep 19, 2010 at 01:58:36PM +0200, Zope Tests Summarizer wrote:
Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Sat Sep 18 23:09:35 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020234.html
$ bin/buildout -c development.cfg ... Updating test-ztk. Getting distribution for 'zope.testrunner'. package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not found (or not a regular file) Creating missing __init__.py for zope.testrunner.testrunner-ex Got zope.testrunner 4.0.0b5. While: Updating test-ztk. Getting distribution for 'zope.testrunner'. Error: Picked: zope.testrunner = 4.0.0b5
You've gotta love buildout's error messages sometimes.
CC> zope.testrunner is test-required by zope.testing (3.9 branch) and zope.component CC> (trunk), but zope.testrunner is not in the ZTK.
CC> So that's a normal error.
CC> I suppose the ZTK should now point to a maintenance bugfix branch of all CC> packages, not the trunk.
I have the feeling that this bot is testing the ZTK trunk/dev and NOT the ZTK 1.0 branch, so having all packages trunk should be right.
You can check here http://buildbot.afpy.org/ztk1.0dev/master.cfg This buildbot uses svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0 but in ZTK 1.0, the [source] section still points to the trunks, so it has no effect. We should now have a maintenance branch for ALL packages, and let the ZTK mr.developer config point to these branches instead of trunk Christophe