getpaid version conflict

Question

installing getpaid for plone, several distributions complained that

We already have: egg.name 0.0 but another.egg 1.2.3 requires 'egg.name>=4.5.6'

I have managed to move forward by pinning the requested versions until:

Error: There is a version conflict.
We already have: zope.component 3.5.1
but zope.site 3.9.2 requires 'zope.component>=3.8.0'.
but zope.browserresource 3.12.0 requires 'zope.component>=3.8.0'.

pinning zope.component to 3.8.0 gives the following:

Error: There is a version conflict.
We already have: zope.component 3.8.0
but five.localsitemanager 1.3 requires 'zope.component<3.6dev'.

How can I circumvent this (catch 22)?

My buildout: http://www.pastie.org/3050771

Answer 1

In general, what is advisable in such a case is to take it step by step. The trick is to add this line to your [buildout] section:

allow-picked-versions = false

This tells zc.buildout to immediately quit when it sees that a package is required that is not pinned. Then you can go to http://pypi.python.org and search for that package and see if you can figure out which version fits best with your other packages and especially your Plone version. On Plone 3 when a zope.* package is not pinned, best is usually to pin it to the oldest version you can find.

In this specific case, those zope.site and zope.browserresource versions are quite recent and require a too new zope.component version.

This is untested, but these pins might work (no guarantees):

zope.site = 3.5.1
zope.component = 3.5.1
zope.browserresource = 3.9.0

Answer 2

Use a KGS (known good set) in your buildout:

• http://good-py.appspot.com/release/getpaid/0.10.4

e.g.

[buildout]
extends = http://good-py.appspot.com/release/getpaid/0.10.4
versions = versions