Hi, Okay, this post started out as a question and then I figured it out as I was writing. But others may run into the same problems so I will post it anyway so your favorite search engine can find it for you when you need it. :)
I did a checkout of the ploneout trunk: svn co https://svn.plone.org/svn/plone/ploneout/trunk ploneout I did the usual python2.4 bootstrap.py and bin/buildout and then ran some tests on a package. All worked fine. Then I wanted to checkout the ploneout 3.0 branch too, so I renamed the current buildout: mv ploneout ploneouttrunk After this, I could not start Zope anymore or run the tests: [EMAIL PROTECTED]:~/buildout/ploneouttrunk $ bin/instance test -s plone.app.layout Traceback (most recent call last): File "bin/instance", line 84, in ? import plone.recipe.zope2instance.ctl File "/home/maurits/buildout-eggs/plone.recipe.zope2instance-1.3-py2.4.egg/plone/recipe/zope2instance/ctl.py", line 37, in ? from Zope.Startup import zopectl ImportError: No module named Zope.Startup Removing all .pyc files did not help, so that was not the problem. The problem was that the bin/instance script and several files within parts/instance had references to the old directory. Makes sense when you think about it. So the solution was to reinstall the instance part of the buildout: bin/buildout install instance Then my tests were running fine again. [Running bin/buildout without any options would have worked too of course; but install the 'instance' part was giving trouble, so a complete bin/buildout was not necessary.] Glad I can put this on my list of things that I know about buildout. ;-) -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl] _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
