Mailing List Archive: Zope: CMF

CMFDefault 2.1.2-beta egg does not install

Index | Next | Previous | View Threaded

wichert at wiggy

Sep 7, 2008, 10:03 PM

Post #1 of 18 (2323 views)
Permalink

CMFDefault 2.1.2-beta egg does not install

While working on plonenext I get an error when trying to install
the Products.CMFDefault egg. This is the buildout -vv output:

Getting required 'Products.CMFDefault'
required by Products.CMFDiffTool 0.4dev.
required by Products.CMFTopic 2.1.2-beta.
required by Products.CMFPlone 3.1.5dev.
Getting distribution for 'Products.CMFDefault'.
We have the best distribution that satisfies 'setuptools'.
Picked: setuptools = 0.6c8
Running easy_install:
/opt/local/Library/Frameworks/Python.framework/Versions/2.4/Resources/Python.app/Contents/MacOS/Python "-c" "from setuptools.command.easy_install import main; main()" "-mUNxd" "/Users/wichert/Development/instances/plonenext/eggs/tmpC1v2O-" "/Users/wichert/Development/instances/plonenext/download/dist/Products.CMFDefault-2.1.2-beta.tar.gz"
path=/Users/wichert/Library/eggs/setuptools-0.6c8-py2.4.egg

Processing Products.CMFDefault-2.1.2-beta.tar.gz
error: None
An error occured when trying to install Products.CMFDefault 2.1.2-beta.Look above this message for any errors thatwere output by easy_install.
While:
Installing instance.
Getting distribution for 'Products.CMFDefault'.
Error: Couldn't install: Products.CMFDefault 2.1.2-beta

Which is not very informative. Does anyone know what might cause this?

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Sep 8, 2008, 12:15 AM

Post #2 of 18 (2259 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 8, 2008, at 07:03 , Wichert Akkerman wrote:

> While working on plonenext I get an error when trying to install
> the Products.CMFDefault egg.

It works fine for me in a simple buildout that installs CMFDefault
into an instance. I get the 2.1.2-beta egg, all the dependencies are
pulled correctly, and the tests run.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkjE0P8ACgkQRAx5nvEhZLKwZgCfScn9dzTaqQWujUpDu5AgAr0t
xu4AoLQyson8dgLQpfb4Yj1eMdav7rki
=XMRw
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

m.van.rees at zestsoftware

Sep 9, 2008, 2:18 AM

Post #3 of 18 (2261 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Wichert Akkerman, on 2008-09-08:
> While working on plonenext I get an error when trying to install
> the Products.CMFDefault egg. This is the buildout -vv output:
(...)
> While:
> Installing instance.
> Getting distribution for 'Products.CMFDefault'.
> Error: Couldn't install: Products.CMFDefault 2.1.2-beta
>
>
> Which is not very informative. Does anyone know what might cause this?

Not very informative indeed. bin/buildout -Nv in plonenext gives me
this more informative output instead:

While:
Installing instance.
Error: There is a version conflict.
We already have: Products.GenericSetup 1.4.1
but Products.CMFActionIcons 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.CMFCalendar 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.CMFCore 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.CMFDefault 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.CMFTopic 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.CMFUid 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
but Products.DCWorkflow 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.

So the question is: why are those products depending on GS 1.3.3? GS
1.4 has been out for a while.

--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 9, 2008, 6:12 PM

Post #4 of 18 (2253 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Maurits van Rees wrote:
> Wichert Akkerman, on 2008-09-08:
> > While working on plonenext I get an error when trying to install
> > the Products.CMFDefault egg. This is the buildout -vv output:
> (...)
> > While:
> > Installing instance.
> > Getting distribution for 'Products.CMFDefault'.
> > Error: Couldn't install: Products.CMFDefault 2.1.2-beta
> >
> >
> > Which is not very informative. Does anyone know what might cause this?
>
> Not very informative indeed. bin/buildout -Nv in plonenext gives me
> this more informative output instead:
>
> While:
> Installing instance.
> Error: There is a version conflict.
> We already have: Products.GenericSetup 1.4.1
> but Products.CMFActionIcons 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.CMFCalendar 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.CMFCore 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.CMFDefault 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.CMFTopic 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.CMFUid 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> but Products.DCWorkflow 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
>
> So the question is: why are those products depending on GS 1.3.3? GS
> 1.4 has been out for a while.

Ah, I complained about that to Jens: he pinned the CMF eggs to an exact
version of GenericSetup, which makes them impossible to use for Plone
which requires a later version.

Can these please be changed to a minimum version requirement instead of
an exact pin?

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 9, 2008, 10:53 PM

Post #5 of 18 (2257 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Wichert Akkerman wrote:
> Previously Maurits van Rees wrote:
> > Wichert Akkerman, on 2008-09-08:
> > > While working on plonenext I get an error when trying to install
> > > the Products.CMFDefault egg. This is the buildout -vv output:
> > (...)
> > > While:
> > > Installing instance.
> > > Getting distribution for 'Products.CMFDefault'.
> > > Error: Couldn't install: Products.CMFDefault 2.1.2-beta
> > >
> > >
> > > Which is not very informative. Does anyone know what might cause this?
> >
> > Not very informative indeed. bin/buildout -Nv in plonenext gives me
> > this more informative output instead:
> >
> > While:
> > Installing instance.
> > Error: There is a version conflict.
> > We already have: Products.GenericSetup 1.4.1
> > but Products.CMFActionIcons 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.CMFCalendar 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.CMFCore 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.CMFDefault 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.CMFTopic 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.CMFUid 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> > but Products.DCWorkflow 2.1.2-beta requires 'Products.GenericSetup==1.3.3'.
> >
> > So the question is: why are those products depending on GS 1.3.3? GS
> > 1.4 has been out for a while.
>
> Ah, I complained about that to Jens: he pinned the CMF eggs to an exact
> version of GenericSetup, which makes them impossible to use for Plone
> which requires a later version.
>
> Can these please be changed to a minimum version requirement instead of
> an exact pin?

I've loosened the version restriction in CMF 2.1 to only use a minimum
version requirement for GenericSetup, which makes it possible to use CMF
with Plone 3.2 and later again.

Jens, can you please cut a new beta egg so we can move forward with
Plone 3.2?

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 9, 2008, 10:53 PM

Post #6 of 18 (2253 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

jens at dataflake

Sep 10, 2008, 2:33 AM

Post #7 of 18 (2254 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 10, 2008, at 07:53 , Wichert Akkerman wrote:

> Previously Wichert Akkerman wrote:
>> Ah, I complained about that to Jens: he pinned the CMF eggs to an
>> exact
>> version of GenericSetup, which makes them impossible to use for Plone
>> which requires a later version.
>>
>> Can these please be changed to a minimum version requirement
>> instead of
>> an exact pin?
>
> I've loosened the version restriction in CMF 2.1 to only use a minimum
> version requirement for GenericSetup, which makes it possible to use
> CMF
> with Plone 3.2 and later again.
>
> Jens, can you please cut a new beta egg so we can move forward with
> Plone 3.2?

There is a reason why originally I pinned the egg at 1.33, and later
relaxed the pin to allow anything 1.3.x: I see test failures with the
1.4.1 egg. Please run the tests with the GS 1.4.1 egg and let me know
what you see. I am seeing errors like this:

<snip>
raise ConfigurationError("Unknown directive", ns, n)
zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "/usr/
local/zope/cmf-21/eggs/Products.GenericSetup-1.4.1-py2.4.egg/Products/
GenericSetup/configure.zcml", line 62.2
ConfigurationError: ('Unknown directive', u'http://namespaces.zope.org/genericsetup'
, u'exportStep')
</snip>

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkjHlFIACgkQRAx5nvEhZLJVvgCdErnPgh8wkcceVWrcvzksL+Uf
xU4An0QP9lX5EmVr9qW01Ii7b9Id7u+f
=d29g
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 10, 2008, 10:43 AM

Post #8 of 18 (2252 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Jens Vagelpohl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Sep 10, 2008, at 07:53 , Wichert Akkerman wrote:
>
> > Previously Wichert Akkerman wrote:
> >> Ah, I complained about that to Jens: he pinned the CMF eggs to an
> >> exact
> >> version of GenericSetup, which makes them impossible to use for Plone
> >> which requires a later version.
> >>
> >> Can these please be changed to a minimum version requirement
> >> instead of
> >> an exact pin?
> >
> > I've loosened the version restriction in CMF 2.1 to only use a minimum
> > version requirement for GenericSetup, which makes it possible to use
> > CMF
> > with Plone 3.2 and later again.
> >
> > Jens, can you please cut a new beta egg so we can move forward with
> > Plone 3.2?
>
> There is a reason why originally I pinned the egg at 1.33, and later
> relaxed the pin to allow anything 1.3.x: I see test failures with the
> 1.4.1 egg. Please run the tests with the GS 1.4.1 egg and let me know
> what you see. I am seeing errors like this:

Is there a conveient buildout I can checkout for this? The cmfout on
plone.org appears to be broken and my current location has incredibly
crappy bandwidth, making every svn access insanely slow, so it's a bit
hard to checkout everything by hand.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

m.van.rees at zestsoftware

Sep 10, 2008, 1:23 PM

Post #9 of 18 (2255 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Jens Vagelpohl, on 2008-09-10:
> There is a reason why originally I pinned the egg at 1.33, and later
> relaxed the pin to allow anything 1.3.x: I see test failures with the
> 1.4.1 egg. Please run the tests with the GS 1.4.1 egg and let me know
> what you see. I am seeing errors like this:
>
>
><snip>
> raise ConfigurationError("Unknown directive", ns, n)
> zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "/usr/
> local/zope/cmf-21/eggs/Products.GenericSetup-1.4.1-py2.4.egg/Products/
> GenericSetup/configure.zcml", line 62.2
> ConfigurationError: ('Unknown directive', u'http://namespaces.zope.org/genericsetup'
> , u'exportStep')
></snip>

I see the same. I suspect that this is only some test setup that is
missing, or a missed loading of the meta.zcml of GenericSetup, but my
testing Fu fails to point me in the right direction here.

GS introduces new features, but I am not aware of any backwards
incompatible changes. Am I correct in that?

--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 10, 2008, 5:19 PM

Post #10 of 18 (2246 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Maurits van Rees wrote:
> Jens Vagelpohl, on 2008-09-10:
> > There is a reason why originally I pinned the egg at 1.33, and later
> > relaxed the pin to allow anything 1.3.x: I see test failures with the
> > 1.4.1 egg. Please run the tests with the GS 1.4.1 egg and let me know
> > what you see. I am seeing errors like this:
> >
> >
> ><snip>
> > raise ConfigurationError("Unknown directive", ns, n)
> > zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "/usr/
> > local/zope/cmf-21/eggs/Products.GenericSetup-1.4.1-py2.4.egg/Products/
> > GenericSetup/configure.zcml", line 62.2
> > ConfigurationError: ('Unknown directive', u'http://namespaces.zope.org/genericsetup'
> > , u'exportStep')
> ></snip>
>
> I see the same. I suspect that this is only some test setup that is
> missing, or a missed loading of the meta.zcml of GenericSetup, but my
> testing Fu fails to point me in the right direction here.
>
> GS introduces new features, but I am not aware of any backwards
> incompatible changes. Am I correct in that?

GS trunk drops some long-deprecated bits which CMF isn't using anyway,
but 1.4 should be fully backwards compatible with 1.3.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 10, 2008, 5:58 PM

Post #11 of 18 (2247 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Jens Vagelpohl wrote:
> There is a reason why originally I pinned the egg at 1.33, and later
> relaxed the pin to allow anything 1.3.x: I see test failures with the
> 1.4.1 egg. Please run the tests with the GS 1.4.1 egg and let me know
> what you see. I am seeing errors like this:
>
>
> <snip>
> raise ConfigurationError("Unknown directive", ns, n)
> zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "/usr/
> local/zope/cmf-21/eggs/Products.GenericSetup-1.4.1-py2.4.egg/Products/
> GenericSetup/configure.zcml", line 62.2
> ConfigurationError: ('Unknown directive', u'http://namespaces.zope.org/genericsetup'
> , u'exportStep')
> </snip>

It was probably pure luck that that used to work before: CMFCore's
testing.py forgot to load meta.zcml from GenericSetup. I've fixed that
and the tests run fine now.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Sep 11, 2008, 12:42 AM

Post #12 of 18 (2246 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

By the way, DCWorkflow needed a similar change to make that same
traceback disappear, which means Wichert was testing CMFCore in
isolation. If possible, could we make sure to test all CMF packages
together when making changes? I'm using a simple buildout that pulls
them all in:

http://svn.dataflake.org/svn/sandboxes/cmf-21/

http://svn.dataflake.org/svn/sandboxes/cmf-trunk/

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkjIy9MACgkQRAx5nvEhZLJ/OgCeJ336V416RlDCgKb84vJ/+HfG
n4kAn1Vx04WGs87eXStNRpkFJVAvpN+r
=xc+j
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

m.van.rees at zestsoftware

Sep 11, 2008, 10:49 AM

Post #13 of 18 (2245 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Jens Vagelpohl, on 2008-09-11:
>
> By the way, DCWorkflow needed a similar change to make that same
> traceback disappear, which means Wichert was testing CMFCore in
> isolation. If possible, could we make sure to test all CMF packages
> together when making changes?

I tested the last changes with a Zope 2.11 instance, with only the CMF
Products, including GenericSetup, in the Products dir. The Products
dir is a checkout of this:

ssh://svn.zope.org/repos/main/CMF/branches/2.1

"bin/zopectl test -s Products" passes for both GS tag 1.3.3 and branch
1.4.

But I get errors when running the CMFDefault and GenericSetup tests
individually.

Running the tests for Products.CMFDefault gives one failure with both
GS versions:

File "/home/maurits/instances/cmf/zope211-cmf21/Products/CMFDefault/browser/document.txt", line 23, in document.txt
Failed example:
browser.open('http://localhost/site/myDocument/@@edit.html')
Exception raised:
Traceback (most recent call last):
...
VocabularyRegistryError

GS 1.3.3. gives 4 errors like this:

ValueError: Index of type DateIndex not found

GS 1.4 gives 13 ComponentLookupErrors:

ComponentLookupError: ('Could not adapt', <Folder at /site>, <InterfaceClass zope.component.interfaces.IComponentLookup>)

> I'm using a simple buildout that pulls them all in:
>
> http://svn.dataflake.org/svn/sandboxes/cmf-21/
>
> http://svn.dataflake.org/svn/sandboxes/cmf-trunk/

Currently this buildout (cmf-21 at least) pulls in
Products.GenericSetup 1.4.1 from the cheese shop. I am curious: why
is it not in the src/ here?

The tests *do* pass there, also the individual ones for CMFDefault and
GS. I don't see what the causes the difference. With Zope 2.11.1 in
that buildout instead of 2.10.6 the test results were the same.

--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

m.van.rees at zestsoftware

Sep 11, 2008, 10:59 AM

Post #14 of 18 (2245 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Maurits van Rees, on 2008-09-11:
> The tests *do* pass there, also the individual ones for CMFDefault and
> GS. I don't see what the causes the difference. With Zope 2.11.1 in
> that buildout instead of 2.10.6 the test results were the same.

Okay, I was using an old Zope 2.11.0 b1. Using 2.11.1 fixes the
errors in CMFDefault.

GS still gives the same errors though. But the instance seems a bit
confused and tries to load some products from the old Zope still, even
though it is a completely new instance. I am puzzled.

Tests for all Products combined pass.

--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 11, 2008, 11:08 AM

Post #15 of 18 (2248 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Maurits van Rees wrote:
> Currently this buildout (cmf-21 at least) pulls in
> Products.GenericSetup 1.4.1 from the cheese shop. I am curious: why
> is it not in the src/ here?

Why should it? GenericSetup is not a real part of CMF and has its own
releases.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 11, 2008, 6:41 PM

Post #16 of 18 (2232 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Jens Vagelpohl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> By the way, DCWorkflow needed a similar change to make that same
> traceback disappear, which means Wichert was testing CMFCore in
> isolation. If possible, could we make sure to test all CMF packages
> together when making changes? I'm using a simple buildout that pulls
> them all in:
>
> http://svn.dataflake.org/svn/sandboxes/cmf-21/
>
> http://svn.dataflake.org/svn/sandboxes/cmf-trunk/

Can you move/copy those to svn.zope.org?

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Sep 12, 2008, 3:05 AM

Post #17 of 18 (2232 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 10, 2008, at 07:53 , Wichert Akkerman wrote:
> Jens, can you please cut a new beta egg so we can move forward with
> Plone 3.2?

Now that we have eggs and releases can be done quickly I'd like to do
away with having several betas. Anyone against calling the current
state 2.1.2 final?

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkjKPwMACgkQRAx5nvEhZLIhVgCgo0J27oJmg8YPMfeP3zf3s0ma
ZakAnjfhkR4ajyXdwnQtiqoMtKQUMvJ/
=CKMT
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Sep 12, 2008, 10:04 AM

Post #18 of 18 (2232 views)
Permalink

Re: CMFDefault 2.1.2-beta egg does not install [In reply to]

Previously Jens Vagelpohl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Sep 10, 2008, at 07:53 , Wichert Akkerman wrote:
> > Jens, can you please cut a new beta egg so we can move forward with
> > Plone 3.2?
>
> Now that we have eggs and releases can be done quickly I'd like to do
> away with having several betas. Anyone against calling the current
> state 2.1.2 final?

No objections here.

Wichert.

--
Wichert Akkerman <wichert [at] wiggy> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF [at] lists
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads