Derek Richardson wrote:
Martin Aspeli wrote:
plone.recipe.plone tracks what's in dist_plone at a time when the
release is made. It should point to the Plone 3 products tarball, and
all the eggs for 3.0 final, with fixed versions.
The best way to peg it, is to do:
[plone]
recipe = plone.recipe.plone==3.0
What are you seeing that makes you think otherwise?
It seems my earlier message didn't make it to the list. Hopefully I am
not repeating what people have already read.
I submitted http://dev.plone.org/plone/ticket/7028 against 3.0-final as
the cause for failing ftests in Vice. I have heard from others that
deleting their buildout caches and rerunning the Vice buildout
(yesterday) allows the ftests to run without errors - i.e., this defect
goes away. I still have a failing buildout on my machine, as I haven't
refreshed my buildout. How can I determine if my buildout contains
3.0-final or another, earlier version?
Look at the generated ./bin/instance script. It'll have a lot of
explicit egg references, where it adds them to the pythonpath. Paste
those here.
Similarly, look at parts/plone/CMFPlone/version.txt and other
version.txt files.
Martin
--
Acquisition is a jealous mistress
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
