-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
-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
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
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
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
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
-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
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
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:
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
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:
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
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'.
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
-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
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.
16 matches
Mail list logo
