Am 24.11.2009, 14:16 Uhr, schrieb Jens Vagelpohl :
> The buildout ties it by extending the versions.cfg file from the Zope 2
> trunk. That versions file contains these overrides:
> zope.app.publisher = 3.9.0
> zope.container = 3.9.0
> zope.publisher = 3.9.0
> zope.site = 3.6.2 # XXX 3.6.3
Hi Charlie,
> 1) How do I tie my buildout to 3.9.0?
> 2) Should we be updating for the change in CMF?
The buildout ties it by extending the versions.cfg file from the Zope 2 trunk.
That versions file contains these overrides:
zope.app.publisher = 3.9.0
zope.container = 3.9.0
zope.publisher = 3.
Am 17.11.2009, 16:22 Uhr, schrieb Hanno Schlichting :
> I just noticed that we already have an appropriate branch / buildout
> at http://svn.zope.org/repos/main/CMF.buildout/branches/zope212-cmf22/
> You might want to use that one. But you probably don't need Zope2 from
> SVN but can use the lates
On Tue, Nov 17, 2009 at 4:00 PM, Charlie Clark wrote:
> Yes, I'm fine with that - how do I fix it? I can then tie my buildout out
> CMF 2.2 beta or release. My buildout.cfg is exactly the same as the
> CMF-sandbox with just my modules being added.
I just noticed that we already have an appropriat
Am 17.11.2009, 15:48 Uhr, schrieb Hanno Schlichting :
Hi Hanno,
> So you are working against Zope 2.13 (trunk) instead of Zope 2.12
> (branches/2.12). Zope 2.13 already has a couple of more changes due to
> the whole Zope Toolkit refactoring.
I can understand that.
> I guess for now running CMF
Hi.
On Tue, Nov 17, 2009 at 3:34 PM, Charlie Clark wrote:
> working on my first CMF-based buildout and I'm getting an error in
> CMFCore.DynamicType
>
> from zope.app.publisher.browser import queryDefaultViewName
> ImportError: No module named publisher.browser
>
> My buildout is almost exactly
