Comment 5 for bug 253377

Okay, this is annoying. I'm not sure I agree that plone.recipe.plone should require an exact version of five.localsitemanager.

In any event, I think this should fix it: In your [plone] section, override the version of localsitemanager that plone.recipe.plone uses with the latest bugfix release:

  [plone]
  recipe = plone.recipe.plone
  eggs =
    five.localsitemanager == 0.4

Please let me know if this fixes your problem.

Considering your concerns about using the latest zope.component; yes, I agree that generally, this can be problematic. But thankfully zope.component is a rather stable piece of software that hardly changes. I hope this version juggling will soon come to an end.

I tried to pin plone.z3cform to not use the latest zope.component in version 0.4 of plone.z3cform, because it the first zope.component 0.5 was really buggy, but then we found out that buildout isn't really intelligent enough with resolving dependencies:

  https://bugs.launchpad.net/zc.buildout/+bug/253260

So I moved plone.z3cform back to using the latest zope.component.