You have some unpinned eggs.
Then buildout tries to get the newest versions. The newest versions
sometimes require newer versions than what plone pinned for you.
set the attribute
allow-picked-versions = False
in your buildout.
Then buildout will start complaining about each egg that has no version
pinning. Add version pinnings accordingly.
That might get a bit tedious, but if you keep that options you will get
repeatable buildouts.
Except when pypi goes down ;-)
Best regards,
Patrick
On Tue, May 18, 2010 at 16:52, Peter.Peng <[email protected]> wrote:
>
> Hi all,
> When I run buildout based on plone3.3.5 and Zope-2.10.11-final-py2.4
> following error of versions confliction was found:
>
> Error: There is a version conflict.
> We already have: zope.component 3.5.1
> but zope.browserpage 3.12.1 requires 'zope.component>=3.7'
>
>
> I just checked the dependcy,it found the confliction is due to the
> following
> eggs defined in
> http://dist.plone.org/release/3.3.5/versions.cfg:
>
> 1) five.localsitemanager = 1.1
> 2) plone.portlet.static = 1.2rc1
>
> the fist one requires zope.component <=3.6
> the second one requires zope.component >=3.7
>
> So what can I do facing such a difficulty because of a hard coding versions
> in config file?
> BTW, I use a exsting Zope installation intead of fetching one,as following
> shows:
> zope2-location = /usr/local/Plone/Zope-2.10.11-final-py2.4
>
>
> Really appreciate your suggestion.
>
> Thanks
> Peter
>
> .
> --
> View this message in context:
> http://plone.293351.n2.nabble.com/Versions-conflict-when-running-buildout-based-on-plone3-3-5-and-Zope-2-10-11-final-py2-4-tp5070365p5070365.html
> Sent from the Product Developers mailing list archive at Nabble.com.
> _______________________________________________
> Product-Developers mailing list
> [email protected]
> http://lists.plone.org/mailman/listinfo/product-developers
>
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
