Am 04.10.2010, 13:58 Uhr, schrieb CMF Tests Summarizer
:
> Subject: FAILED (failures=3) : CMF-trunk Zope-2.12 Python-2.6.5 : Linux
> From: CMF Tests
> Date: Sun Oct 3 21:54:31 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-October/013610.html
Me again: forgot to commit my update
Am 03.10.2010, 13:58 Uhr, schrieb CMF Tests Summarizer
:
> Subject: FAILED (failures=3, errors=5) : CMF-trunk Zope-2.12
> Python-2.6.5 : Linux
> From: CMF Tests
> Date: Sat Oct 2 21:56:16 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-October/013606.html
Mine, of course, but n
Am 25.09.2010, 17:05 Uhr, schrieb Charlie Clark
:
> Relates to two changes I made yesterday which should now be resolved, at
> least I can't reproduce them here.
ah, yuppie fixed things for me. Thanks!
Charlie
--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmho
Am 25.09.2010, 13:58 Uhr, schrieb CMF Tests Summarizer
:
> Subject: FAILED (errors=3) : CMF-trunk Zope-2.12 Python-2.6.5 : Linux
> From: CMF Tests
> Date: Fri Sep 24 21:54:46 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-September/013574.html
Relates to two changes I made yester
Am 27.06.2010, 13:58 Uhr, schrieb CMF Tests Summarizer
:
> Subject: FAILED (failures=1) : CMF-trunk Zope-2.12 Python-2.6.5 : Linux
> From: CMF Tests
> Date: Sat Jun 26 21:52:14 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-June/013216.html
My fault - wrong permssion on @@logged_
Hi!
Tres Seaver wrote:
> I also don't know why the 'instance' and 'i18n*' parts are configured in
> these buildouts -- does somebody have a memory of why, or a reason to
> keep them?
I don't use the 'instance' part. For manual testing I prefer using
mkzopeinstance.
The 'i18n*' parts provide an
Am 31.03.2010, 22:07 Uhr, schrieb Tres Seaver :
>> The "instance" part is a pure convenience to quickly fire up an instance
>> if I need to look at something in the ZMI while doing development. If
>> there's no pressing reason to remove it I'd really like to keep it.
> I can see leaving that alone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 22:07 , Tres Seaver wrote:
> Jens Vagelpohl wrote:
>> On 3/31/10 20:33 , Tres Seaver wrote:
>>> I also don't know why the 'instance' and 'i18n*' parts are configured in
>>> these buildouts -- does somebody have a memory of why, or a reason t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
> On 3/31/10 20:33 , Tres Seaver wrote:
>> I also don't know why the 'instance' and 'i18n*' parts are configured in
>> these buildouts -- does somebody have a memory of why, or a reason to
>> keep them?
>
> The "instance" part is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 20:33 , Tres Seaver wrote:
> I also don't know why the 'instance' and 'i18n*' parts are configured in
> these buildouts -- does somebody have a memory of why, or a reason to
> keep them?
The "instance" part is a pure convenience to quickly
On Wed, Mar 31, 2010 at 8:33 PM, Tres Seaver wrote:
> OK, the change I'm planning on the trunk essentially reverts your last
> commit (all the extra version pins to make the 'test-zope212' part
> build), plus deleting the test-zope212 part (see attached patch).
Sure. That wasn't much more than a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> 2010/3/31 Tres Seaver :
>> I believe the root of this problem is that the 'index' and 'versions'
>> bits of a buildout.cfg are effectively Highlanders ("there can only be
>> one"). I gave up on trying to get the "two, two, t
2010/3/31 Tres Seaver :
> I believe the root of this problem is that the 'index' and 'versions'
> bits of a buildout.cfg are effectively Highlanders ("there can only be
> one"). I gave up on trying to get the "two, two, two Zopes in one"
> buildout to work, and instead created a separate buildout.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Hanno Schlichting wrote:
>> Hi Tres,
>
>> On Wed, Mar 31, 2010 at 5:02 PM, Tres Seaver wrote:
>>> I can't even get the trunk buildout to build this morning: Hanno, do
>>> you have any clue what is going on here?
>>>
>>> The ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> Hi Tres,
>
> On Wed, Mar 31, 2010 at 5:02 PM, Tres Seaver wrote:
>> I can't even get the trunk buildout to build this morning: Hanno, do
>> you have any clue what is going on here?
>>
>> The version, 3.7.1, is not consist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CMF Tests Summarizer wrote:
> Test failures
> -
>
> Subject: FAILED (errors=13) : CMF-trunk Zope-trunk Python-2.6.4 : Linux
> From: CMF Tests
> Date: Tue Mar 30 21:52:10 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-March/
16 matches
Mail list logo
