Re: [Zope-dev] zope-tests - FAILED: 6, OK: 28, UNKNOWN: 3

2012-05-14 Thread Christophe Combelles

I've safe-upgraded and restarted the machine recently, but now it shows up:
http://buildbot.afpy.org/ztk1.0dev/waterfall

Christophe


Le 14/05/2012 03:13, Tres Seaver a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/13/2012 09:00 PM, Zope tests summarizer wrote:

[6]UNKNOWN UNKNOWN : ZTK 1.0dev / Python2.4.6 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2012-May/062965.html


[7]UNKNOWN UNKNOWN : ZTK 1.0dev / Python2.5.5 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2012-May/062964.html


[8]UNKNOWN UNKNOWN : ZTK 1.0dev / Python2.6.7 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2012-May/062966.html


I can't tell what is up with these builds:  the linked buildbot page
doesn't display.  Cristophe, can you please check?



Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+wXCsACgkQ+gerLs4ltQ4WeACfVMijzipUO0sdvAamFpfk4lDz
k/UAnjSZRVBZY1pUKli8JC2igJOg5qVM
=P1Kj
-END PGP SIGNATURE-



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 8, OK: 39

2011-11-14 Thread Christophe Combelles
Le 14/11/2011 01:52, Christophe Combelles a écrit :
 Le 13/11/2011 14:22, Tres Seaver a écrit :
 [1]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-November/052554.html

 This is the same hour-long timeout as yesterday in the buildout step:

 mr.developer: Updated 'zope.viewlet' with subversion.

 command timed out: 3600 seconds without output, killing pid 22071
 process killed by signal 9 program finished with exit code -1
 elapsedTime=4054.018485

 I have no idea what is failing.


 [2]FAILED  Zope 3.4 KGS / Python2.4.6 64bit linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052563.html


 [3]FAILED  Zope 3.4 KGS / Python2.5.5 64bit linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052564.html


 [4]FAILED  Zope 3.4 Known Good Set / py2.4-32bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052550.html


 [5]FAILED  Zope 3.4 Known Good Set / py2.4-64bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052548.html


 [6]FAILED  Zope 3.4 Known Good Set / py2.5-32bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052559.html


 [7]FAILED  Zope 3.4 Known Good Set / py2.5-64bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052552.html

 If somebody who cares about the KGS could look at these failures and
 figure out why knew versions are slipping into the mix, that would be
 great.  Otherwise, we should just quit testing it.

 The initial build process of the kgs has no versions pinned, so it was being
 built with some of the latests libs that fail under python2.4.  I have added
 versions in the toplevel buildout.cfg so that it shouldn't fail again.

 I don't know if someone is interested but we have enough minor versions 
 upgrade
 available to be able to release a maintenance versions of the KGS: 3.4.2

fixed

http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/441







 [8]FAILED  winbot / z3c.form_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2011-November/052551.html

 Stephan said yesterday he thought this was a chameleon bug.  I just
 tried to reproduce this on a Linux box with a fresh checkout, using
 Python 2.5.5.  The tests don't even run for me::

 Traceback (most recent call last):
 File /tmp/zft/bin/test, line 26, inmodule
   '--test-path', '/tmp/zft/src',
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
  line 30, in run
   failed = run_internal(defaults, args, script_parts=script_parts)
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
  line 41, in run_internal
   from zope.testrunner.runner import Runner
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/runner.py, 
 line 46, inmodule
   import zope.testrunner.tb_format
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/tb_format.py,
  line 19, inmodule
   import zope.exceptions.exceptionformatter
 File 
 /tmp/zft/eggs/zope.exceptions-3.6.1-py2.5.egg/zope/exceptions/__init__.py,
  line 24, inmodule
   import zope.security
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/__init__.py,
  line 17, inmodule
   from zope.security.management import checkPermission
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/management.py,
  line 20, inmodule
   from zope.security import interfaces
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/interfaces.py,
  line 19, inmodule
   from zope.schema import Text, TextLine
 File 
 /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/__init__.py, line 
 16, inmodule
   from zope.schema._field import Field, Container, Iterable, Orderable
 File /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/_field.py, 
 line 78
   class SourceText(Text):
   ^
 SyntaxError: invalid syntax



 Tres.
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 8, OK: 39

2011-11-14 Thread Christophe Combelles
Le 14/11/2011 23:24, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/14/2011 04:50 PM, Christophe Combelles wrote:
 Le 14/11/2011 01:52, Christophe Combelles a écrit :
 Le 13/11/2011 14:22, Tres Seaver a écrit :

 If somebody who cares about the KGS could look at these failures
 and figure out why knew versions are slipping into the mix, that
 would be great.  Otherwise, we should just quit testing it.

 The initial build process of the kgs has no versions pinned, so it
 was being built with some of the latests libs that fail under
 python2.4.  I have added versions in the toplevel buildout.cfg so
 that it shouldn't fail again.

 I don't know if someone is interested but we have enough minor
 versions upgrade available to be able to release a maintenance
 versions of the KGS: 3.4.2

 fixed

 http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/441

 I

 don't understand why r123334 was needed to fix the KGS buildout:  I
 thought the KGS was pinned by virtue of using its 'versions.cfg' file:

   http://download.zope.org/zope3.4/3.4.1/versions.cfg

The problem doesn't come from the KGS itself, but from the package that creates 
the KGS, I mean zope.release. (which itself depends on the logic of zope.kgs).
During the release process, zope.release generates a buildout that will be used 
to launch tests. So there are 2 buildouts : the one from zope.release itself, 
and the one generated by the generate-buildout command.



 (Actually, I don't know what the intended relationship is between that
 file and http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg ).

The versions.cfg is generated from the controlled-packages file, and contains 
only the latest versions.  controlled-packages was supposed to track all the 
compatible versions (even older ones) of the KGS.
But it happens to be mathematically wrong and impossible, because the 
cobinatory 
explosion of versions makes it unrealistic to handle all the combinations.



 Actually, I thought we were supposed to have a PyPI-like index which
 ensured that no unwanted versions would creep in, e.g.::

   http://download.zope.org/zope3.4/3.4.1/index/

 Can somebody who remembers how that dance was supposed to work enlighten us?


Everything is here
http://svn.zope.org/zope.release/branches/3.4/README.txt?rev=89181view=auto

This is much simpler with the ZTK now.



 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAk7BlRMACgkQ+gerLs4ltQ7YhwCg2g8n/s26u0z5FvkrgwtTV+z8
 ExQAoLrqxIAdMhQ+G1skUR2o7qa6LoOA
 =BrQZ
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 13, OK: 40

2011-10-31 Thread Christophe Combelles
Le 31/10/2011 15:31, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 10/31/2011 04:43 AM, Wichert Akkerman wrote:
 On 10/31/2011 07:21 AM, Tres Seaver wrote:
 These are all failures in the following zopeapp test::

 -  zope/app/applicationcontrol/tests/test_zope_version.py
  def test_WrongLocale(self): Demonstrate bug
 177733 currentPath =
 os.path.dirname(os.path.abspath(__file__)) if isSVNAvailable()
 and isSVNCheckout(currentPath): zv = ZopeVersion(currentPath)
 zv.getZopeVersion() # check that we don't get a
 'Development/Unknown' version
 self.assert_(zv.result.startswith('Development/Revision: ')) -
 --



 I have no theory for how that test could suddenly start failing (nor
 even what it is really supposed to test).  It doesn't fail on my
 machine on any version of Python.

 Different version of subversion installed perhaps?


 Hmmm, that would seem odd.  Christophe, has that machine recently
 updated its subversion (between the test runs reported Saturday night
 and those reported last night)?

I've launched the test with a pdb in zopeversion.py, and it looks like a locale 
problem.

(Pdb) !print self._getSVNInfoOutput().read()
Chemin?\194?\160: 
/home/ccomb/ztk1.1dev-slave/Python2.7.2-Linux-64bit/build/src/zope.app.applicationcontrol/src/zope/app/applicationcontrol/tests
URL?\194?\160: 
svn://svn.zope.org/repos/main/zope.app.applicationcontrol/trunk/src/zope/app/applicationcontrol/tests
Racine du d?\195?\169p?\195?\180t?\194?\160: svn://svn.zope.org/repos/main
UUID du d?\195?\169p?\195?\180t?\194?\160: 62d5b8a3-27da-0310-9561-8e5933582275
R?\195?\169vision?\194?\160: 123191
Type de n?\197?\147ud?\194?\160: r?\195?\169pertoire
T?\195?\162che programm?\195?\169e?\194?\160: normale
Auteur de la derni?\195?\168re modification?\194?\160: menesis
R?\195?\169vision de la derni?\195?\168re modification?\194?\160: 121717
Date de la derni?\195?\168re modification: 2011-05-18 21:23:30 +0200 (Wed 18 
May 
2011)

Then :

(Pdb) print info
{'UUID du d?\\195?\\169p?\\195?\\180t?\\194?\\160': 
'62d5b8a3-27da-0310-9561-8e5933582275', 'Date de la derni?\\195?\\168re 
modification': '2011-05-18 21:23:30 +0200 (Wed 18 May 2011)', 
'R?\\195?\\169vision de la derni?\\195?\\168re modification?\\194?\\160': 
'121717', 'Racine du d?\\195?\\169p?\\195?\\180t?\\194?\\160': 
'svn://svn.zope.org/repos/main', 'Type de n?\\197?\\147ud?\\194?\\160': 
'r?\\195?\\169pertoire', 'T?\\195?\\162che programm?\\195?\\169e?\\194?\\160': 
'normale', 'Auteur de la derni?\\195?\\168re modification?\\194?\\160': 
'menesis', 'URL?\\194?\\160': 
'svn://svn.zope.org/repos/main/zope.app.applicationcontrol/trunk/src/zope/app/applicationcontrol/tests',
 
'Chemin?\\194?\\160': 
'/home/ccomb/ztk1.1dev-slave/Python2.7.2-Linux-64bit/build/src/zope.app.applicationcontrol/src/zope/app/applicationcontrol/tests',
 
'R?\\195?\\169vision?\\194?\\160': '123191'}

(Pdb) info.get(Revision, )
''

The key is not the same.
It just means the method to read svn data is not robust.



For the Data.fs problem, I had removed all the Data.fs* from all the builders, 
but they all came back again:

ccomb@boa:~$ find . -name 'Data.fs*'
./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.lock
./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.tmp
./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.index
./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs
./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.lock
./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.tmp
./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.index
./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs
./ztk1.1-slave/Python2.7.2-Linux-64bit/build/Data.fs.lock
./ztk1.1-slave/Python2.7.2-Linux-64bit/build/Data.fs.tmp
./ztk1.1-slave/Python2.7.2-Linux-64bit/build/Data.fs.index
./ztk1.1-slave/Python2.7.2-Linux-64bit/build/Data.fs
./ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.lock
./ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.tmp
./ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.index
./ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs
./ztk1.0dev-slave/Python2.6.7-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.lock
./ztk1.0dev-slave/Python2.6.7-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.tmp
./ztk1.0dev-slave/Python2.6.7-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.index
./ztk1.0dev-slave/Python2.6.7-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs
./ztk1.0dev-slave/Python2.7.2-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.lock
./ztk1.0dev-slave/Python2.7.2-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.tmp
./ztk1.0dev-slave/Python2.7.2-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs.index
./ztk1.0dev-slave/Python2.7.2-Linux-64bit/build/parts/test-ztk-zope.session/Data.fs

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 37

2011-10-29 Thread Christophe Combelles
Le 28/10/2011 19:21, Tres Seaver a écrit :
The failures here look to be due to binary incompatbility (old Python
was UCS4, new one is UCS2) in already-built eggs.  Christophe, can you
please remove any 'py2.6-linux-x86_64' eggs and let them get rebuilt?

done

 So, except for the binary eggs built under the UCS4 Python 2.6.5 not
 working with the new UCS2 Python 2.6.7, we have exactly the one
 failure left to deal with.  Looking more closely:  that failure occurs
 on the very last line of 'setupstack.txt', where the working directory
 has been restored:  thus, the issue is that there are 'Data.fs' files
 in the *main working trees* on the buildbot.afpy.org machine.
 Christophe, can you please find and remove such files?

done too

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope-tests - FAILED: 7, OK: 41

2011-10-26 Thread Christophe Combelles
Le 26/10/2011 03:57, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Woohoo -- down to just seven!


 [1]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051688.html

 This

 has the sub-process buffer failure for which I checked in a fix
 today from Jonathan Ballet:  I'm hopeful that it clears up tomorrow.

 This run also has the unexpected Data.fs in a tempdir failure.


 [2]FAILED  ZTK 1.1 / Python2.6.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051687.html

 This

 run has the same two failures, plus the command-line error for
 the 'cProfile' option.  Christophe, can you please verify that the
 Python 2.6.5 used to run these tests was built from source, and has
 the 'cProfile.py' module?  I suspect we may be using a system Python
 on an OS which splits out the devtools into a separate OS-level
 distribution (e.g., 'python-dev' or some such).


It's a system python 2.6.5 indeed, I'm replacing it with a new build of 2.6.7

Christophe




 [3]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051686.html

 This

 run has only the unexpected Data.fs failure.


 [4]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051703.html

 Same

 failures as #1.


 [5]FAILED  ZTK 1.1dev / Python2.6.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051701.html

 Same

 failures as #2.


 [6]FAILED  winbot / z3c.form_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2011-October/051704.html

 I'm

 ignoring this one, except to note that it is *not* lxml related.


 [7]FAILED  winbot / ztk_dev py_254_win32
 https://mail.zope.org/pipermail/zope-tests/2011-October/051719.html

 This

 build should be disabled:  the ZTK trunk is no longer compatible
 with Python 2.5.


 So, in summary, we can get back to a green board if we can figure
 out the three distinct errors here:

 - - A 'Data.fs' present in what is supposed to be a newly-created tempdir,
in zope.testrunner/src/zope/testrunner/testrunner-subunit.txt.

 - - The subprocess buffer failure I hope I fixed today.

 - - THe 'cProfile' issue, only on ccomb's Python 2.6.5.




 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAk6naScACgkQ+gerLs4ltQ51EwCeIpofX9MxjDUJhzNTWg4YGA4l
 WCQAoJabPy9M7l4TQOL14mE35Oj1HI3C
 =c3wo
 -END PGP SIGNATURE-


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] buildbots should have an svn info step

2010-09-23 Thread Christophe Combelles
Le 22/09/2010 11:49, Patrick Gerken a écrit :
 On Wed, Sep 22, 2010 at 00:54, Marius Gedminasmar...@gedmin.as  wrote:
 On Tue, Sep 21, 2010 at 04:33:35PM +0200, Adam GROSZER wrote:
 Hello Patrick,

Could you nag the buildbot maintainers to add an svn info step for
their bots?

The issue is that you can get the svn URL only from the bot config,
which is not always available.

 Patrick asked me a while ago to switch to using mode='clobber', which
 means the initial checkout step always does an rm -rf followed by an svn
 checkout with the full URL.

 Yes, but some rightfully objected that creates lots of traffic. I
 think it would be nice if everybody
 sweeps their slaves contents once in a while, like weekly.


I just added a weekly cleanup cron for the slaves


 I also really like the svn info step.
 I have seen ccomb has something a bit more advanced, but I have to
 check that again.

I've copied it from Marius' buildbot conf (pov.lt). It can be either done with 
a 
inherited SVN build step which redefines the createSummary method. But the 
actual one is a custom LastChange Step.
See http://buildbot.afpy.org/ztk1.0dev/master.cfg


 Apart from that, I think it was your idea, that everybody should try
 to trigger their buildbots at the same time, like midnight GMT. That
 sounds also good.

I've moved the time around midnight

Christophe



 Next week I will go through the current buildbot list and collect some
 more information, and contact each one individually. This week I won't
 find the time.

 Best regards,

   Patrick



 Marius Gedminas
 --
 http://pov.lt/ -- Zope 3/BlueBream consulting and development

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)

 iEYEARECAAYFAkyZN4YACgkQkVdEXeem14/m4ACePID0XyNjE8oWd+LwxAjACQg1
 dZ8An3m61AwCgwkdlUk+m2yGW4p2h01t
 =5+MJ
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )




 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 12 Failed

2010-09-21 Thread Christophe Combelles
Le 20/09/2010 17:19, Adam GROSZER a écrit :
 Hello Christophe,

 Monday, September 20, 2010, 4:53:16 PM, you wrote:

 CC  Le 19/09/2010 15:45, Marius Gedminas a écrit :
 On Sun, Sep 19, 2010 at 01:58:36PM +0200, Zope Tests Summarizer wrote:
 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Sat Sep 18 23:09:35 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020234.html

   $ bin/buildout -c development.cfg
   ...
   Updating test-ztk.
   Getting distribution for 'zope.testrunner'.
   package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not 
 found (or not a regular file)
   Creating missing __init__.py for zope.testrunner.testrunner-ex
   Got zope.testrunner 4.0.0b5.
   While:
 Updating test-ztk.
 Getting distribution for 'zope.testrunner'.
   Error: Picked: zope.testrunner = 4.0.0b5

 You've gotta love buildout's error messages sometimes.


 CC  zope.testrunner is test-required by zope.testing (3.9 branch) and 
 zope.component
 CC  (trunk), but zope.testrunner is not in the ZTK.

 CC  So that's a normal error.

 CC  I suppose the ZTK should now point to a maintenance bugfix branch of all
 CC  packages, not the trunk.

 I have the feeling that this bot is testing the ZTK trunk/dev and NOT
 the ZTK 1.0 branch, so having all packages trunk should be right.

You can check here http://buildbot.afpy.org/ztk1.0dev/master.cfg

This buildbot uses svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0
but in ZTK 1.0, the [source] section still points to the trunks, so it has no 
effect.

We should now have a maintenance branch for ALL packages, and let the ZTK 
mr.developer config point to these branches instead of trunk

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 12 Failed

2010-09-21 Thread Christophe Combelles
Le 21/09/2010 10:44, Hanno Schlichting a écrit :
 On Tue, Sep 21, 2010 at 10:41 AM, Christophe Combellescc...@free.fr  wrote:
 This buildbot uses svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0
 but in ZTK 1.0, the [source] section still points to the trunks, so it has no
 effect.

 We should now have a maintenance branch for ALL packages, and let the ZTK
 mr.developer config point to these branches instead of trunk

 I'm not sure I agree. I think it's perfectly fine to create the
 branches only once actually required. Such a moment would be now for
 possible one or two packages.


Ok, so the buildbot is failing for good reasons. That means we should create a 
maintenance branch only for the failing packages?




 Hanno


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 42 OK, 12 Failed

2010-09-20 Thread Christophe Combelles
Le 19/09/2010 15:45, Marius Gedminas a écrit :
 On Sun, Sep 19, 2010 at 01:58:36PM +0200, Zope Tests Summarizer wrote:
 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Sat Sep 18 23:09:35 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020234.html

  $ bin/buildout -c development.cfg
  ...
  Updating test-ztk.
  Getting distribution for 'zope.testrunner'.
  package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not 
 found (or not a regular file)
  Creating missing __init__.py for zope.testrunner.testrunner-ex
  Got zope.testrunner 4.0.0b5.
  While:
Updating test-ztk.
Getting distribution for 'zope.testrunner'.
  Error: Picked: zope.testrunner = 4.0.0b5

 You've gotta love buildout's error messages sometimes.


zope.testrunner is test-required by zope.testing (3.9 branch) and 
zope.component 
(trunk), but zope.testrunner is not in the ZTK.

So that's a normal error.

I suppose the ZTK should now point to a maintenance bugfix branch of all 
packages, not the trunk.

Christophe



 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Sat Sep 18 23:09:53 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020235.html

 Same error.

 Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Sat Sep 18 23:09:54 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020236.html

 Same error.

 Marius Gedminas



 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] buidout 1.5

2010-09-17 Thread Christophe Combelles
There are some discussions in the grok and bluebream lists about the 
opportunity 
to upgrade to buildout 1.5, as it will provide *isolation without virtualenv*, 
so it should facilitate installations and deployments.

Is it too late for the ZTK 1.0?
Is it worth at least trying to see what it does?

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Toolkit - new 1.0 branch

2010-09-17 Thread Christophe Combelles
Le 17/09/2010 16:50, Gediminas Paulauskas a écrit :
 2010/9/17 Christophe Combellescc...@free.fr:
 Le 14/09/2010 11:49, Hanno Schlichting a écrit :
 Hi.

 After the release of the ZTK 1.0c1 I also created a maintenance branch
 for the ZTK 1.0. The branch can be found at:

 svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0

 just done for http://buildbot.afpy.org/ztk1.0/

 Please, also switch http://buildbot.afpy.org/ztk1.0dev/

 You may need to remove checkouts of packages that were switched to
 stable branches. mr.developer will tell you that on first build.

thanks for looking

I've also switched this one, it's currently building
http://buildbot.afpy.org/ztk1.0dev/waterfall



 Next build for ztk1.0dev builders are scheduled in 132 hours, this is
 a very long interval. I thought they were supposed to be nightly.

I had set it weekly because it was supposed to break more often. I've set it 
again to nightly.



 Also, I wanted to look at
 http://buildbot.afpy.org/ztk1.0dev/master.cfg to see what the
 configuration is, but master.cfg files are no longer publicly
 available at that location.

It's available again. It has disappeared after migration to buildbot 0.8.1



 Gediminas


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Toolkit - new 1.0 branch

2010-09-16 Thread Christophe Combelles
Le 14/09/2010 11:49, Hanno Schlichting a écrit :
 Hi.

 After the release of the ZTK 1.0c1 I also created a maintenance branch
 for the ZTK 1.0. The branch can be found at:

 svn://svn.zope.org/repos/main/zopetoolkit/branches/1.0

just done for http://buildbot.afpy.org/ztk1.0/

btw thanks for releasing 1.0c1!

Christophe


 Please update the buildbots to test this branch under all of Python
 2.4, 2.5 and 2.6.

 The trunk is now open to development of the ZTK 1.1. Please adjust the
 buildbots to test the trunk on Python 2.5, 2.6 and 2.7. Python 2.4 is
 no longer supported for the ZTK 1.1 release but we like to get Python
 2.7 support.

 On behalf of the ZTK release team,
 Hanno


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 46 OK, 7 Failed, 2 Unknown

2010-09-16 Thread Christophe Combelles
Le 16/09/2010 15:06, Michael Howitz a écrit :
 Am 16.09.2010 um 13:33 schrieb Patrick Gerken:
 I believe, nobody had yet the chance to change the configuration to
 follow the branch.
 that buildbot still follows the trunk.

 The name is ZTK 1.0 so it should test the branch or
 change its name and drop testing py24 as this is no longer supported by ZTK 
 trunk.


I've just changed it, and svn switched the slaves. Let's wait for the next build




 On Thu, Sep 16, 2010 at 13:12, Michael Howitzm...@gocept.com  wrote:
 Am 15.09.2010 um 13:58 schrieb Zope Tests Summarizer:
 [...]
 Test failures
 -
 [...]
 Subject: FAILED : ZTK 1.0 / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Wed Sep 15 01:26:59 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020028.html

 Which SVN-URL does this buildbout use for buildout? Sorry, I did not find 
 any hint in the buildbot UI.


 Yours sincerely,
 --
 Michael Howitz · m...@gocept.com · software developer
 gocept gmbh  co. kg · forsterstraße 29 · 06112 halle (saale) · germany
 http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1
 Zope and Plone consulting and development

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )


 Mit freundlichen Grüßen
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 26 OK, 15 Failed, 2 Unknown

2010-08-25 Thread Christophe Combelles
Le 25/08/2010 11:18, Marius Gedminas a écrit :

 FWIW I had to downgrade virtualenv back to 1.3.3, since 1.4.5 uses Distribute
 by default, and zc.zope3recipes 0.6.2 doesn't like Distribute:

 File 
 /var/lib/buildbot/eggs/zc.zope3recipes-0.6.2-py2.4.egg/zc/zope3recipes/README.txt,
  line 78, in README.txt
 Failed example:
  print system(join('bin', 'buildout')),
 Expected:
  Develop: '/sample-buildout/demo1'
  Develop: '/sample-buildout/demo2'
  Installing myapp.
  Generated script '/sample-buildout/parts/myapp/runzope'.
  Generated script '/sample-buildout/parts/myapp/debugzope'.
 Got:
  Develop: '/sample-buildout/demo1'
  install_dir /sample-buildout/develop-eggs/tmpGFC-Sdbuild
  Develop: '/sample-buildout/demo2'
  install_dir /sample-buildout/develop-eggs/tmpIidjYCbuild
  Installing myapp.
  Generated script '/sample-buildout/parts/myapp/runzope'.
  Generated script '/sample-buildout/parts/myapp/debugzope'.


I suppose this should be fixed in Distribute instead. Just a matter of not 
displaying install_dir.



 Looks like the outer buildout.cfg doesn't pin zc.buildout so it always
 gets the latest version, and the inner one doesn't like that at all.  I
 think the fix is to change buildout steps to do this instead:
 ...
  $ cd test  ../sandbox/bin/python ../bootstrap.py  bin/buildout

 (instead of cd test  ../bin/buildout)

 This was the right fix.

 Marius Gedminas



 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 35 OK, 11 Failed, 1 Unknown

2010-08-22 Thread Christophe Combelles
This failure seems to be introduced by zope.testing 3.9.5, but only for python 
2.6

Le 22/08/2010 13:58, Zope Tests Summarizer a écrit :
 Summary of messages to the zope-tests list.
 Period Sat Aug 21 12:00:00 2010 UTC to Sun Aug 22 12:00:00 2010 UTC.
 There were 47 messages: 6 from Zope Tests, 1 from buildbot at 
 enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at 
 winbot.zope.org, 8 from ccomb at free.fr, 5 from ct at gocept.com, 10 from 
 jdriessen at thehealthagency.com.


 Test failures
 -

 Subject: FAILED : ZTK 1.0 / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Sun Aug 22 01:38:48 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018770.html

test-ztk-zope.server failed with:
/home/ccomb/ztk1.0-slave/Python2.6.5-Linux-64bit/build/bin/test-ztk-zope.server:30:
 
DeprecationWarning: zope.testing.testrunner is deprecated in favour of 
zope.testrunner.
   import zope.testing.testrunner
/home/ccomb/buildout-eggs/zope.testing-3.9.5-py2.6.egg/zope/testing/testrunner/formatter.py:28:
 
DeprecationWarning: zope.testing.exceptions is deprecated in favour of 
zope.testrunner.exceptions
   from zope.testing.exceptions import DocTestFailureException
/home/ccomb/buildout-eggs/zope.server-3.6.2-py2.6.egg/zope/server/tests/test_serverbase.py:18:
 
DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python 
standard library doctest module
   from zope.testing import doctest
Running zope.testing.testrunner.layer.UnitTests tests:
   Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.


Failure in test testHELP (zope.server.ftp.tests.test_ftpserver.Tests)
Traceback (most recent call last):
   File /usr/lib/python2.6/unittest.py, line 279, in run
 testMethod()
   File 
/home/ccomb/buildout-eggs/zope.server-3.6.2-py2.6.egg/zope/server/ftp/tests/test_ftpserver.py,
 
line 278, in testHELP
 self.assertEqual(self.execute('HELP', 1), result)
   File /usr/lib/python2.6/unittest.py, line 350, in failUnlessEqual
 (msg or '%r != %r' % (first, second))
AssertionError: '214-The following commands are recognized\r\n' != '214-The 
following commands are recognized\r\nHelp goes here somewhen.\r\n214 Help 
done.\r\n'

   Ran 83 tests with 1 failures and 0 errors in 9.140 seconds.
Tearing down left over layers:
   Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.



 Subject: FAILED : winbot / ZODB_dev py_270_win32
 From: buildbot at winbot.zope.org
 Date: Sun Aug 22 03:10:24 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018774.html

 Subject: FAILED : winbot / ZODB_dev py_270_win64
 From: buildbot at winbot.zope.org
 Date: Sun Aug 22 04:05:57 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018775.html


 Unknown
 ---

 Subject: [zodb-tests] buildbot failure in Enfold Systems on 
 zodb-trunk-python-2.6-maestro
 From: buildbot at enfoldsystems.com
 Date: Sun Aug 22 03:00:50 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018773.html


 Tests passed OK
 ---

 Subject: OK : Zope Buildbot / zope2.12 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 19:58:56 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018729.html

 Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 19:59:34 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018730.html

 Subject: OK : Zope Buildbot / zope2 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:01:01 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018731.html

 Subject: OK : Zope Buildbot / zope2 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:02:08 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018732.html

 Subject: OK : Zope Buildbot / ztk_win slave-win
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:02:55 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018733.html

 Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:07:15 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018734.html

 Subject: OK : Zope Buildbot / ztk slave-osx
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:07:44 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018735.html

 Subject: OK : Zope Buildbot / zope2 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:10:09 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018736.html

 Subject: OK : Zope Buildbot / ztk slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:10:38 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018737.html

 Subject: OK : Zope Buildbot / ztk slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sat Aug 21 20:17:40 EDT 

Re: [Zope-dev] Zope Tests: 42 OK, 12 Failed

2010-08-20 Thread Christophe Combelles
Le 20/08/2010 13:58, Zope Tests Summarizer a écrit :
 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Aug 19 23:30:51 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018664.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Aug 19 23:31:15 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018665.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Aug 19 23:31:34 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018666.html

these should run only once a week.
I just forgot to hg up after migrating to the new server.


 Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 64bit linux
 From: ccomb at free.fr
 Date: Fri Aug 20 00:00:05 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018667.html

 Subject: FAILED : Zope 3.4.1 KGS / Python2.5.5 64bit linux
 From: ccomb at free.fr
 Date: Fri Aug 20 00:00:08 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018668.html

same pb. It's fixed
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 49 OK, 13 Failed, 1 Unknown

2010-08-14 Thread Christophe Combelles
I've moved the buildbots from an old 32bit to a new 64bit and 
virtualization-capable server, so there is a mix of the results from the old 
and 
new ones.
Now the old ones are stopped.

http://buildbot.afpy.org/

I've also added the autorelease buildbot (Discover new ZTK 1.0 automatically)

Christophe

Le 14/08/2010 14:01, Zope Tests Summarizer a écrit :
 Summary of messages to the zope-tests list.
 Period Fri Aug 13 12:00:00 2010 UTC to Sat Aug 14 12:00:00 2010 UTC.
 There were 63 messages: 6 from Zope Tests, 1 from buildbot at 
 enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at 
 winbot.zope.org, 19 from ccomb at free.fr, 20 from jdriessen at 
 thehealthagency.com.


 Test failures
 -

 Subject: FAILED (failures=1) : Zope-trunk Python-2.6.5 : Linux
 From: Zope Tests
 Date: Fri Aug 13 21:39:43 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018342.html

 Subject: FAILED : winbot / ztk_dev py_244_win32
 From: buildbot at winbot.zope.org
 Date: Fri Aug 13 22:08:30 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018348.html

 Subject: FAILED : winbot / ztk_dev py_254_win32
 From: buildbot at winbot.zope.org
 Date: Fri Aug 13 22:15:49 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018350.html

 Subject: FAILED : winbot / ztk_dev py_265_win32
 From: buildbot at winbot.zope.org
 Date: Fri Aug 13 22:22:23 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018353.html

 Subject: FAILED : winbot / ztk_dev py_265_win64
 From: buildbot at winbot.zope.org
 Date: Fri Aug 13 22:29:12 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018354.html

 Subject: FAILED : winbot / ztk_10 py_244_win32
 From: buildbot at winbot.zope.org
 Date: Fri Aug 13 22:37:26 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018356.html

 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Fri Aug 13 23:35:38 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018360.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Fri Aug 13 23:36:10 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018361.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Fri Aug 13 23:37:01 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018362.html

 Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 64bit linux
 From: ccomb at free.fr
 Date: Sat Aug 14 00:00:43 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018363.html

 Subject: FAILED : Zope 3.4.1 KGS / Python2.5.5 64bit linux
 From: ccomb at free.fr
 Date: Sat Aug 14 00:01:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018364.html

 Subject: FAILED : winbot / ZODB_dev py_270_win32
 From: buildbot at winbot.zope.org
 Date: Sat Aug 14 03:10:58 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018376.html

 Subject: FAILED : winbot / ZODB_dev py_270_win64
 From: buildbot at winbot.zope.org
 Date: Sat Aug 14 04:06:40 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018378.html


 Unknown
 ---

 Subject: [zodb-tests] buildbot failure in Enfold Systems on 
 zodb-trunk-python-2.6-maestro
 From: buildbot at enfoldsystems.com
 Date: Sat Aug 14 04:00:12 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018377.html


 Tests passed OK
 ---

 Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:20:09 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018326.html

 Subject: OK : Zope Buildbot / zope2 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:21:55 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018327.html

 Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:24:46 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018328.html

 Subject: OK : Zope Buildbot / zope2 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:26:45 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018329.html

 Subject: OK : Zope Buildbot / ztk slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:27:07 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018330.html

 Subject: OK : Zope Buildbot / ztk slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:32:50 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018331.html

 Subject: OK : Zope Buildbot / ztk_win slave-win
 From: jdriessen at thehealthagency.com
 Date: Fri Aug 13 10:33:06 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/018332.html

 Subject: OK : Zope Buildbot / zope2.12 slave-osx
 From: jdriessen at 

Re: [Zope-dev] Zope Tests: 75 OK, 15 Failed, 1 Unknown

2010-08-02 Thread Christophe Combelles
Le 02/08/2010 14:00, Zope Tests Summarizer a écrit :
 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Aug  1 23:50:36 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017766.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Aug  1 23:51:40 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017767.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Aug  1 23:52:18 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017768.html

Changes in zope.testing requires adding zope.testrunner to the KGS, and it's 
not 
possible while there is no 1.0 branch.   Instead of having a failure every day, 
I will run this test once a week.  Anyway, people can manually trigger the 
builders at any time.



 Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Mon Aug  2 01:28:17 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017772.html

This one looks like a timeout. I've raised it to 3600s.


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-30 Thread Christophe Combelles
 Hi Christophe,

 Christophe Combelles wrote:

 [snip: z3c.testsetup test errors on bluebream]

 thanks!! There is only one remaining error on Python 2.4 now. It seems 
 related
 to an 'encoding' argument added to DocFileSuite in python 2.5, and used in
 zope.app.testing

 Oh, missed that. This is more tricky but I'll have a look into it.
 Thanks for the hint (and the buildbots revealing such nasty problems)!

Thanks for releasing 0.8.1. It seemed to fix it!

However I have a weird problem: builders were all green, then I suddenly had 
repeated failures with 0.8.1 on all the builders, then I've tried to launch the 
tests by myself directly in the builder, and tests passed, without changing 
anything... Then if I relaunch the builder alone, tests pass:
http://buildbot.afpy.org/bluebream/waterfall

Is there a possibility that tests fail when several builders run at the same 
time?




File 
/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/README.txt,
 
line 110, in README.txt
Failed example:
 testrunner.run(defaults)
Differences (ndiff with -expected +actual):
 - Running z3c...layer.DefaultZCMLLayer [...ftesting.zcml] tests:
 -   Set up z3c...layer.DefaultZCMLLayer [...ftesting.zcml] in N.NNN 
seconds.
 + Running z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
tests:
 +   Set up z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
in N.NNN seconds.
 Ran 3 tests with 0 failures and 0 errors in N.NNN seconds.
 - Running z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] tests:
 -   Tear down z3c...layer.DefaultZCMLLayer [...ftesting.zcml] ... not 
supported
 + Running z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
tests:
 +   Tear down z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting.zcml]
 
... not supported
 Running in a subprocess.
 -   Set up z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] in N.NNN 
seconds.
 +   Set up z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
in N.NNN seconds.
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 -   Tear down z3c...layer.DefaultZCMLLayer [...ftesting2.zcml] ... not 
supported
 +   Tear down z3c.testsetup.functional.layer.DefaultZCMLLayer 
[/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/ftesting2.zcml]
 
... not supported
   Running z3c.testsetup.tests.othercave.testing.FunctionalLayer1 tests:
 Running in a subprocess.
 Set up z3c.testsetup.tests.othercave.testing.FunctionalLayer1 in N.NNN 
seconds.
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 Tear down z3c.testsetup.tests.othercave.testing.FunctionalLayer1 in 
N.NNN seconds.
   Running z3c.testsetup.tests.othercave.testing.UnitLayer2 tests:
 Running in a subprocess.
 Set up z3c.testsetup.tests.othercave.testing.UnitLayer1 in N.NNN 
seconds.
 Set up z3c.testsetup.tests.othercave.testing.UnitLayer2 in N.NNN 
seconds.
   Running testSetUp of UnitLayer1
   Running testSetUp of UnitLayer2
   Running testTearDown of UnitLayer2
   Running testTearDown of UnitLayer1
 Ran 1 tests with 0 failures and 0 errors in N.NNN seconds.
 Tear down z3c.testsetup.tests.othercave.testing.UnitLayer2 in N.NNN 
seconds.
 Tear down z3c.testsetup.tests.othercave.testing.UnitLayer1 in N.NNN 
seconds.
 - Running zope...testrunner.layer.UnitTests tests:
 ?  ^
 + Running zope.testing.testrunner.layer.UnitTests tests:
 ?  ^^^
 Running in a subprocess.
 -   Set up zope...testrunner.layer.UnitTests in N.NNN seconds.
 ?   ^
 +   Set up zope.testing.testrunner.layer.UnitTests in N.NNN seconds.
 ?   ^^^
 - Custom setUp for  DocTest doctest05.txt from ...doctest05.txt:0 (2 
examples)
 - Custom tearDown for  DocTest doctest05.txt from ...doctest05.txt:0 
(2 examples)
 + Custom setUp for  DocTest doctest05.txt from 
/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/doctest05.txt:0
 
(2 examples)
 + Custom tearDown for  DocTest doctest05.txt from 
/home/ccomb/buildout-eggs/z3c.testsetup-0.8.1-py2.6.egg/z3c/testsetup/tests/othercave/doctest05.txt:0
 
(2 examples)
 Ran 4 tests with 0 failures and 0 errors in N.NNN seconds.
 -   Tear down zope...testrunner.layer.UnitTests in N.NNN seconds

[Zope-dev] ZTK automatic discovery with buildbots

2010-07-27 Thread Christophe Combelles
I've worked on a special buildbot that would be able to create a new ZTK list 
automatically, by testing arbitrary new versions. For this purpose I've created 
z3c.checkversions, and the last version 0.4 has two new options (--blacklist 
and 
--incremental). http://pypi.python.org/pypi/z3c.checkversions/0.4

I'm using this package in the special following buildbot:
http://buildbot.afpy.org:8018/waterfall

Previously, the buildbot was testing the set of *all the latest* releases, but 
I 
was never able to get success. So I've changed its behaviour and now it's 
testing new packages one by one, and reduces the version number until tests 
pass :

1) The first builder on the left uses z3c.checkversions to create a new list 
with *only one* new version, and reject any version found in a blacklist.
2) The 3 builders in the middle do the actual tests against this list. If some 
build fails, the package is added in the blacklist.
3) if tests pass, the version list is kept for the following builds.


The buildbot has started living by itself, and has given the following 
behaviour :

- it started with ZTK 1.0a2
- it upgraded (arbitrary) zope.dublincore 3.6.0 - 3.6.3
- tests failed
- it added zope.dublincore 3.6.3 in the blacklist
- it upgraded zope.dublincore 3.6.0 - 3.6.2
- tests failed
- it added zope.dublincore 3.6.2 in the blacklist
- it upgraded zope.dublincore 3.6.0 - 3.6.1
- tests failed
- it added zope.dublincore 3.6.1 in the blacklist
- so it keeps zope.dublincore 3.6.0 (until 3.6.4 is released)
- it upgraded lxml 2.2.6 - 2.2.7
- tests passed
- lxml 2.2.7 is kept for future builds (mmh, ok it wasn't, but it should be :( )
The next run will try another package, and we should be able to get the best 
working ZTK automatically. I still need to do this for all platforms...

This is not optimal, because zope.dublincore 3.6.3 maybe works well when 
upgraded with another package, but I'm not sure how to detect this.

Any idea or suggestion welcome.

Christophe


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZTK automatic discovery with buildbots

2010-07-27 Thread Christophe Combelles
Le 27/07/2010 19:57, Christophe Combelles a écrit :
 - lxml 2.2.7 is kept for future builds (mmh, ok it wasn't, but it should be 
 :( )

I've fixed it, now it does keep lxml=2.2.7, and it just chose 
zope.testing=3.9.5.

The chosen package is visible in the stdio of the 1st builder :

(...)
z3c.recipe.compattest=0.12.2
zope.testing=3.9.5 # was: 3.9.4
zope.authentication=3.7.1
(...)


 The next run will try another package, and we should be able to get the best
 working ZTK automatically. I still need to do this for all platforms...

 This is not optimal, because zope.dublincore 3.6.3 maybe works well when
 upgraded with another package, but I'm not sure how to detect this.

 Any idea or suggestion welcome.

 Christophe


 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Python 2.7 buildbot reports

2010-07-24 Thread Christophe Combelles
Le 24/07/2010 17:36, Adam GROSZER a écrit :
 Hello Hanno,

 Saturday, July 24, 2010, 3:30:53 PM, you wrote:


 HS  If the various buildbot maintainers have enough time and are around,
 HS  they could disable Python 2.7 for now and add it back once we got the
 HS  ZTK 1.0 branch.

 done for winbot


done for ztk1.0 and ztk1.0dev too

I'm also in the process of changing the server used for the buildbots, it will 
be 64bits by default, and support virtualization. So I'll try to set up 32bit 
again, then.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-24 Thread Christophe Combelles
Le 24/07/2010 03:51, Uli Fouquet a écrit :
 Hi there,

 Christophe Combelles wrote:
 Le 14/07/2010 11:28, Baiju M a écrit :
 On Wed, Jul 14, 2010 at 2:57 PM, Baiju Mmba...@zeomega.com   wrote:
 On Sun, Jul 11, 2010 at 5:49 PM, Christophe Combellescc...@free.fr   
 wrote:
 Le 11/07/2010 13:59, Zope Tests Summarizer a écrit :


 Subject: FAILED : Bluebream / Python2.4.6 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:05:41 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016427.html

 Subject: FAILED : Bluebream / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:33 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016428.html

 Subject: FAILED : Bluebream / Python2.6.4 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:34 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016429.html


 This is a failure in z3c.testsetup. Can someone have a look at it? It 
 also fails
 with 0.7.0.

 FYI: In trunk, if I pin zc.recipe.testrunner to 1.2.0, this failure is
 going away.

 I mean the trunk of z3c.testsetup

 Ok thanks, I've also checked that.

 Can someone release a new version of z3c.testsetup (say 0.8)?
 Or add me as owner so I can do it?  (pypi: ccomb)

 Sorry for reacting so slowly and thanks for the hint!

 Just released z3c.testsetup 0.8 and tests seem to work again at least on
 my test system with Linux 32-bit and with different ZTKs. Locally also
 bluebream seems to be happy with the new piece.

 Instead of pinning zc.recipe.testrunner I took the liberty to fix the
 tests. Hope that works for other constellations as well.


thanks!! There is only one remaining error on Python 2.4 now. It seems related 
to an 'encoding' argument added to DocFileSuite in python 2.5, and used in 
zope.app.testing

Christophe



 I also added you as owner of the package on PyPI, to avoid such a
 blocking situation next time.

 Best regards,


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.testsetup test faliure (was Re: Zope Tests: 55 OK, 18 Failed)

2010-07-22 Thread Christophe Combelles
Le 14/07/2010 11:28, Baiju M a écrit :
 On Wed, Jul 14, 2010 at 2:57 PM, Baiju Mmba...@zeomega.com  wrote:
 On Sun, Jul 11, 2010 at 5:49 PM, Christophe Combellescc...@free.fr  wrote:
 Le 11/07/2010 13:59, Zope Tests Summarizer a écrit :


 Subject: FAILED : Bluebream / Python2.4.6 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:05:41 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016427.html

 Subject: FAILED : Bluebream / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:33 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016428.html

 Subject: FAILED : Bluebream / Python2.6.4 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:34 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016429.html


 This is a failure in z3c.testsetup. Can someone have a look at it? It also 
 fails
 with 0.7.0.

 FYI: In trunk, if I pin zc.recipe.testrunner to 1.2.0, this failure is
 going away.

 I mean the trunk of z3c.testsetup

Ok thanks, I've also checked that.

Can someone release a new version of z3c.testsetup (say 0.8)?
Or add me as owner so I can do it?  (pypi: ccomb)

regards,
Christophe


 Regards,
 Baiju M



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Python 2.7 buildbot reports

2010-07-22 Thread Christophe Combelles
Considering recent discussions on Python 2.7 support, should we disable the 
failure reports for Python 2.7?  (6 failures out of 17 in the last report)



Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Python 2.7 buildbot reports

2010-07-22 Thread Christophe Combelles
Le 22/07/2010 19:30, Adam GROSZER a écrit :
 Hello Christophe,

 I think they should definitely STAY for trunk's, for release version
 we need to clear which releases support which pythons and set builders
 accordingly.
 Anyway, we **should specify** what to test with the bots, I think it's
 a small chaos now.

Currently, there are 2 ZTK tests:

ZTK 1.0dev : tests all the package trunks of the zopetoolkit trunk
ZTK 1.0 : tests all the package releases of the zopetoolkit trunk

Both are interesting, ZTK 1.0dev allows to detect early breakages, before any 
release. Trunks should not break during development.



 Thursday, July 22, 2010, 6:07:16 PM, you wrote:

 CC  Considering recent discussions on Python 2.7 support, should we disable 
 the
 CC  failure reports for Python 2.7?  (6 failures out of 17 in the last 
 report)



 CC  Christophe
 CC  ___
 CC  Zope-Dev maillist  -  Zope-Dev@zope.org
 CC  https://mail.zope.org/mailman/listinfo/zope-dev
 CC  **  No cross posts or HTML encoding!  **
 CC  (Related lists -
 CC   https://mail.zope.org/mailman/listinfo/zope-announce
 CC   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 55 OK, 18 Failed

2010-07-11 Thread Christophe Combelles
Le 11/07/2010 13:59, Zope Tests Summarizer a écrit :


 Subject: FAILED : Bluebream / Python2.4.6 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:05:41 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016427.html

 Subject: FAILED : Bluebream / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:33 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016428.html

 Subject: FAILED : Bluebream / Python2.6.4 32bit linux
 From: ccomb at free.fr
 Date: Sat Jul 10 22:07:34 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016429.html


This is a failure in z3c.testsetup. Can someone have a look at it? It also 
fails 
with 0.7.0.

regards
Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Toolkit - 1.0a1 release

2010-07-10 Thread Christophe Combelles
Le 06/07/2010 16:38, Jan-Wijbrand Kolman a écrit :
 On 6/30/10 21:47 PM, Hanno Schlichting wrote:
 To use the ZTK release, you can use:

 [buildout]
 extends =
   http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg
   http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg

 This first release focuses on getting something out and defining the
 actual technical outcome of a release. Currently the release outcome
 is tailored to the needs of the three frameworks.

 Grok's groktoolkit now extends from this 1.0a1 release. After today's
 zc.catlog bugfix release, Grok is using the ZTK now without any issues.

Same thing for BlueBream: the next version 1.0b3 will be using the ZTK 1.0a2. 
And There is no bbkit anymore. Eveything is in the bluebream package.

Christophe


 Thanks Hanno!

 regards, jw

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] access to download.zope.org (for bluebream)

2010-07-10 Thread Christophe Combelles
Hi,

I would like to release Bluebream 1.0b3. May I have scp access to 
download.zope.org in order to upload the new version file?

regards,
Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Including Paste into the ZTK version list?

2010-07-09 Thread Christophe Combelles
Le 09/07/2010 16:50, Hanno Schlichting a écrit :
 Hi.

 I noticed that all three frameworks (BB, Grok, Zope2) have version
 pins for Paste, PasteDeploy and PasteScript. Does anyone object to
 including them into the ztk-versions.cfg under dependencies?

 It's currently:

 Paste = 1.7.4
 PasteDeploy = 1.3.3
 PasteScript = 1.7.3

OK for bluebream, I'm currently modifying it so that it depends on the ZTK, and 
I'll be happy with anything reducing the buildout.

with the few remaining packages, I get errors on z3c.testsetup tests. Is there 
anyone else having this problem?

Christophe


 Note that Paste 1.7.4 addresses a security issue [1], so you should
 update it regardless.

 Hanno

 [1] 
 http://pylonshq.com/articles/archives/2010/6/paste_174_released_addresses_xss_security_hole
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] [ZTK] toolchain versions

2010-07-09 Thread Christophe Combelles
Hi,

http://svn.zope.org/zopetoolkit/trunk/ztk-versions.cfg?rev=114375view=auto

is there any reason why the versions pinning of the toolchain are in the 
ztk-versions.cfg ?  Packages such as z3c.recipe.depgraph, mr.developer, 
z3c.checkversions have nothing to do with the final frameworks nor the ZTK.

Shouldn't they be isolated to a [versions] section in the buildout?

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [ZTK] toolchain versions

2010-07-09 Thread Christophe Combelles
Le 09/07/2010 18:44, Hanno Schlichting a écrit :
 Hi.

 On Fri, Jul 9, 2010 at 6:37 PM, Christophe Combellescc...@free.fr  wrote:
 http://svn.zope.org/zopetoolkit/trunk/ztk-versions.cfg?rev=114375view=auto

 is there any reason why the versions pinning of the toolchain are in the
 ztk-versions.cfg ?  Packages such as z3c.recipe.depgraph, mr.developer,
 z3c.checkversions have nothing to do with the final frameworks nor the ZTK.

 Shouldn't they be isolated to a [versions] section in the buildout?

 We talked about this in one of our meetings :)

 Having the toolchain inside the ztk-versions.cfg makes it easier to
 extend the ZTK. Zope 2 just has to use a single extends= line and Grok
 just two (for the additional zopeapp-versions.cfg).

 Since we all use the toolchain anyways, we didn't see a point in
 separating them out.

ok, maybe it was the meeting when I was not there.
I'm ok with it, because it (again) reduces the custom version list of everyone.

But it looks like we have a list of 33 packages which are not really part of 
the 
ZTK, which is finally very close to having an extra.cfg :)



 Hanno



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Python 2.7 on the apfy buildbots

2010-07-09 Thread Christophe Combelles
The afpy buildbots now all run a slave with Python 2.7 final
http://buildbot.afpy.org/

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Python 2.7 on the apfy buildbots

2010-07-09 Thread Christophe Combelles
Le 09/07/2010 21:04, Christophe Combelles a écrit :
 The afpy buildbots now all run a slave with Python 2.7 final
 http://buildbot.afpy.org/

However, the 2.7 slaves don't send any alert to the zope-tests list. Should I 
enable this?



 Christophe
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 31 OK, 5 Failed

2010-06-19 Thread Christophe Combelles
Le 12/06/2010 15:35, Tres Seaver a écrit :

 Very strange.  BlueBream tests pass only on Python 2.4.x, KGS 3.4.1
 tests fail only on that same version.  Can somebody who works with those
 projects day-to-day help diagnose?

 - - The BB failures appear to be due to having zope.testing missing, or
mis-installed:  I have no idea why the build step doesn't fail.


These BB failures should be now fixed, the buildout was vulnerable to new 
versions, I've pinned them and forbid picked versions.

Christophe

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Developer meeting in IRC tomorrow at 15:00 UTC

2010-06-19 Thread Christophe Combelles
Le 16/06/2010 16:32, Christian Theune a écrit :
 Me again, :)

 here's the summary from yesterday:

 - the first MSDN license is around, others are still waiting
 - work on the windows egg builder is in progress, as is the buildbot
 slave setup for the rackspace machine
 - supporting Python 2.7 needs help from the buildbot owners and

I've upgraded all the afpy buildbots to use Python 2.7rc1
http://buildbot.afpy.org/

Christophe

 requires a review of RestrictedPython
 - all participants of the bug day are invited to write a short summary
 after concluding their bug day so we get an overview of what happened
 - the index view of download.zope.org is autogenerated now

 The full minutes should be available here, shortly:
 http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100615.html

 Christian


___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 17 OK, 2 Failed

2010-05-30 Thread Christophe Combelles
Le 30/05/2010 15:33, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Adam GROSZER wrote:
 ZTS  Test failures
 ZTS  -

 ZTS  Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux
 ZTS  From: ccomb at free.fr
 ZTS  Date: Sun May 30 00:29:38 EDT 2010
 ZTS  URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014714.html

 Huhh?
 Last change was 4 days ago.
 Let's see what happens tonight.

 That looks like a (maybe transient) bug in either zdaemon itself or
 (more likely) in its tests.

There is something wrong with zdaemon tests:
Now I have no builder running, but:
$ ps -ef | grep zdaemon | wc -l
74

They all look like this:
ccomb18951 1  0 May20 ?00:00:06 
/home/ccomb/slave4/Python2.5.2-32bit-linux/build/test/../sandbox/bin/python 
./zdaemon -S 
/home/ccomb/buildout-eggs/zdaemon-2.0.4-py2.5.egg/zdaemon/schema.xml -C conf 
tail -f data

Another big problem is /tmp filling with crap:
$ ls -1 /tmp/ | grep tmp | wc -l
3726

I will restart the server to clean everything, but we should find a solution 
for 
that.

Christophe





 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkwCaS8ACgkQ+gerLs4ltQ4ipACgnN2A03Qxi3pVd0cf37+7qO19
 GEcAn0S1qgUGes/2GYe7Vh1jYN6KKp5t
 =RTb1
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 12 OK, 7 Failed

2010-05-23 Thread Christophe Combelles
Le 24/05/2010 01:34, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Zope Tests Summarizer wrote:
 Summary of messages to the zope-tests list.
 Period Sat May 22 12:00:00 2010 UTC to Sun May 23 12:00:00 2010 UTC.
 There were 19 messages: 6 from Zope Tests, 12 from ccomb at free.fr, 1 from 
 ct at gocept.com.


 Test failures
 -

 Subject: FAILED: Repository policy check found errors in 583 projects
 From: ct at gocept.com
 Date: Sat May 22 21:17:43 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014567.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Sat May 22 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014578.html

 This is a build failure, due conflict markers in the ztk.cfg file.

Thanks for watching,
I've moved the svn revert one step higher, above the bootstrap.



 Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Sat May 22 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014579.html

 Likewise.

 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Sat May 22 23:00:26 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014580.html

 Likewise.

 Subject: FAILED : ZTK 1.0 / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Sun May 23 01:54:02 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014583.html

 The 'test-ztk' failures here look like they need new releases of the
 following packages with the Python 2.4 doctest-compatibility fixes:

 - - zope.browserpage (maybe just this one)
 - - zope.viewlet
 - - zope.contentprovider

 The 'test-zopeapp' failure here and in the next two should go away once
 I release the updated version of zope.app.wsgi tonight.


 Subject: FAILED : ZTK 1.0 / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Sun May 23 01:54:57 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014584.html

 Subject: FAILED : ZTK 1.0 / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Sun May 23 01:55:28 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014585.html



 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkv5u4AACgkQ+gerLs4ltQ5/4ACgqLwzijxcybB20oV5eZZsXml6
 GysAn13nQ/JxZJ0RzuNx93N89RvkzX67
 =cK1I
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] buildbots on IRC

2010-05-22 Thread Christophe Combelles
The buildbots are now notifying #zope and #zope3-dev
Their nicknames are

- bbot_kgs341
- bbot_ztk10dev
- bbot_ztk10

You can discuss with them with a set of commands, with either public or private 
messages. You can ask their status, force a build, etc... Example:

(16:51:00) ccomb: bbot_ztk10: commands
(16:51:00) bbot_ztk10: buildbot commands: commands, dance, destroy, excited, 
force, hello, help, join, last, leave, list, notify, source, status, stop, 
version, watch

The buildbot for the BlueBream template is only notifying #bluebream.

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] buildbot for ZTK released packages (linux 32)

2010-05-19 Thread Christophe Combelles
It's live again. This one tests only released packages: 
http://buildbot.afpy.org/ztk1.0/waterfall

Failures :

python2.4 : zope
- zope.browserpage
- zope.viewlet
- zope.contentprovider
- zope.defferedimport
- zope.app.wsgi

python 2.5 and 2.6 :
- zope.app.wsgi

python2.7b2 :
- zope.testing
- zope.formlib
- zope.proxy
- zope.exceptions
- zope.app.publisher
- zope.app.wsgi
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] [Zope3-Users] [ANN] Zope 3.4.1b2 KGS released

2010-05-17 Thread Christophe Combelles
Le 17/05/2010 13:40, Adam GROSZER a écrit :
 Hello,

 It's available here:
 http://download.zope.org/zope3.4/3.4.1b2/index.html

 Docs and changelog should be now up to date.

 Schedule is to have a 3.4.1c1 on May 21th, final 3.4.1 on May 28th.

thanks!

Below is the list of available bugfix versions found by z3c.checkversions:

$ wget http://download.zope.org/zope3.4/3.4.1b2/versions.cfg

$ checkversions -l 2 versions.cfg
Checking buildout file versions.cfg
zope.dottedname=3.4.6
z3c.i18n=0.1.2
zope.app.security=3.5.3
zope.dublincore=3.4.3
z3c.optionstorage=1.0.7
z3c.formui=1.4.3
z3c.pagelet=1.0.3
zope.lifecycleevent=3.4.1
zope.i18nmessageid=3.5.2
zope.app.testing=3.4.5
zope.minmax=1.1.2
z3c.traverser=0.2.5
z3c.layer=0.2.5
zope.app.externaleditor=3.4.0-r81494
z3c.formjs=0.4.1
ClientForm=0.2.10
zope.app.twisted=3.4.2
zope.app.zapi=3.4.1
setuptools=0.6.12
mechanize=0.1.11
zope.rdb=3.4.2
zope.testbrowser=3.4.4
zope.app.i18n=3.4.6
RestrictedPython=3.5.2
zc.resourcelibrary=1.0.2
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ztk checkversions script

2010-05-16 Thread Christophe Combelles
Le 04/05/2010 00:04, Christophe Combelles a écrit :
 Vincent Fretin a écrit :
 On Sun, May 2, 2010 at 10:52 PM, Martijn Faassenfaas...@startifact.com  
 wrote:
 Hi there,

 Of course what applies to Hanno should apply to others making releases
 of packages maintained by the Zope Toolkit project as well. I think the
 ZTK leadership should figure out some kind of guidelines for this that
 people can follow. Maybe someone can write a tool too to check up how
 far a toolkit is out of sync with the latest releases. Just some ideas.

 For the tool, I think I did it already. I modified one of Hanno's
 script some times ago:
 cd zopetoolkit/trunk
 bin/buildout -c checknew.cfg
 bin/python checknew.py

 I have already started to turn this script into a buildout recipe (probably
 z3c.recipe.checknew).
 I will make sure it can discover either minor bugfix versions or major 
 versions,
 and be able to create a versions.cfg.

It's now released as z3c.checkversions
http://pypi.python.org/pypi/z3c.checkversions

It's not a recipe but a console_script. So that it can be used in a virtualenv 
as well, without buildout.

For a buildout, you just have to add it in the buildout eggs: it creates a 
checkversions script that can detect new versions (minor or major, depending on 
the -l option).

Christophe


 Christophe


 Vincent
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )



 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
   https://mail.zope.org/mailman/listinfo/zope-announce
   https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 12 OK, 6 Failed

2010-05-05 Thread Christophe Combelles
Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Zope Tests Summarizer wrote:
 Summary of messages to the zope-tests list.
 Period Tue May  4 12:00:00 2010 UTC to Wed May  5 12:00:00 2010 UTC.
 There were 18 messages: 6 from Zope Tests, 11 from ccomb at free.fr, 1 from 
 ct at gocept.com.


 Test failures
 -

 Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux
 From: ccomb at free.fr
 Date: Tue May  4 11:37:59 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014264.html
 
 This fails due to using 'distribute' instead of 'setuptools' (and the
 failing doctest looks exceptionally useless).

I've updated the build yesterday to use setuptools, the last build for 
Python2.4 
succeeded.

 
 Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Tue May  4 12:02:12 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014265.html
 
 Likewise this one.

There is just 1 remaining failure now.

 
 Subject: FAILED: Repository policy check found errors in 670 projects
 From: ct at gocept.com
 Date: Tue May  4 21:16:40 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014266.html
 
 Expected failures.  Once the others clear, we need to start shaming
 folks into cleaning up the copyrights.
 
 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Wed May  5 00:12:38 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014277.html
 
 This one dies inside the test-zopeapp phase with:
 
  command timed out: 1200 seconds without output, killing pid 20016


Ok, I'm raising the timeout to 3600s for test-ztk and test-zopeapp.

thanks for having watched!
Christophe


 
 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Wed May  5 00:14:13 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014278.html
 
 This one dies the same way.
 
 Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux
 From: ccomb at free.fr
 Date: Wed May  5 00:57:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014281.html
 
 
 
 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iEYEARECAAYFAkvhnGsACgkQ+gerLs4ltQ50FQCfVoLRC6oagtbJHGDq7BKSc2hw
 t9wAoMbjUqvGZOUesGqqjbJ4re/OaoKu
 =lvFf
 -END PGP SIGNATURE-
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] ztk checknew script

2010-05-03 Thread Christophe Combelles
Vincent Fretin a écrit :
 On Sun, May 2, 2010 at 10:52 PM, Martijn Faassen faas...@startifact.com 
 wrote:
 Hi there,

 Of course what applies to Hanno should apply to others making releases
 of packages maintained by the Zope Toolkit project as well. I think the
 ZTK leadership should figure out some kind of guidelines for this that
 people can follow. Maybe someone can write a tool too to check up how
 far a toolkit is out of sync with the latest releases. Just some ideas.
 
 For the tool, I think I did it already. I modified one of Hanno's
 script some times ago:
 cd zopetoolkit/trunk
 bin/buildout -c checknew.cfg
 bin/python checknew.py

I have already started to turn this script into a buildout recipe (probably 
z3c.recipe.checknew).
I will make sure it can discover either minor bugfix versions or major 
versions, 
and be able to create a versions.cfg.

Christophe

 
 Vincent
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] summary of suggestions

2010-05-03 Thread Christophe Combelles
Thanks for these suggestions. This is *exactly* what we (the ztk release team) 
need.

Are there other recommendations from other people?

Martijn Faassen a écrit :
 Hi there,
 
 Because my suggestions (besides the fork issue) as a ZTK 
 user/contributor were scattered through the thread, here's a handy summary:
 
 * please construct guidelines for updating the ZTK when making a release
of a package that's managed by the ZTK project. It's useful people
test their changes within the ZTK.
 
 * please let these guidelines not block most updates by most people
most of the time; it should be easy to update the ZTK. Gatekeepers
tend to slow things down a lot, and we don't have them for most Python
code.

We have already started discussing about this. One idea is to let the ZTK 
update 
or even release by itself, with the help of the buildbot infrastructure.
I would like to replace the expected ztk bureaucracy with automated scripts 
that 
enforce some rules and *help* people. Particularly the implicit rules that make 
people upset when they are not respected. One example is the first message of 
the previous thread ;)

The Zope ecosystem and its processes has become quite complex, and we cannot 
expect people to never do errors or to know or read everything.

 
 * there's a 'checknew.py' script to see whether there are releases newer
than the ZTK. I'd be useful if this were integrated
in the standard ZTK buildout.cfg so you just get a 'bin/checknew'.
It'd also be nice if that were reusable by other toolkit projects.


It's on the way. It will probably take the buildout.cfg as an argument, to 
allow 
checking different buildout files with possibly different versions.


 
 * (new idea) similarly it'd be nice if there were a script integrated
that could check which binary egg releases exist for Windows (32 bit,
64 bit,
Python version). Right now BlueBream is maintaining a list here:
 
http://wiki.zope.org/bluebream/StatusOfWindowsBinaryPackages
 
 * Please update the ZTK documentation about the status of the ZTK
steering group and the ZTK release team. It's unclear to newcomers
such as myself.
 
 * In general it'd be useful if the release team recorded decisions
in the ZTK documentation. It's confusing to have to go look for them
in mailing list archives and people tend to forget or reinterpret
decisions as time goes by.

Ok, we will write down decisions or status somewhere. We are just starting 
organizing ourselves.

Christophe

 
 Regards,
 
 Martijn
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed, 2 Unknown

2010-05-03 Thread Christophe Combelles
Hanno Schlichting a écrit :
 On Mon, May 3, 2010 at 8:02 PM, Tres Seaver tsea...@palladion.com wrote:
 Breakage in the following packages, but only on Python 2.4, and only in
 doctests:

 - - zope.browserpage
 - - zope.viewlet
 - - zope.contentprovider
 - - zope.deferredimport

 At least the first one is due to doctests not exposing an '__file__' in
 their faux-module globals under 2.4.  We might need to add Lennart's
 monkeypatch under 2.4, or else drop 2.4 support altogether.
 
 Hhm. I'm inclined to drop 2.4 support here. Using a zope.testing that
 tries to be compatible all the way from 2.4 to 3.1 is quite a bit of a
 stretch.

Unless I missed something, the ZTK was globally compatible with Python2.4 
recently, wasn't it?  Do we want the latest changes and Lennart's work to be 
part of the ZTK 1.0?

If not, the svn branches used for the ZTK 1.0dev should be updated to point to 
a 
maintenance branch.
(I suppose it's our job)

Christophe

 
 Hanno
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 10 OK, 6 Failed

2010-05-02 Thread Christophe Combelles
Christophe Combelles a écrit :
 Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Zope Tests Summarizer wrote:

 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:24 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html

 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html
 Christophe,

 These failures appear to be due to a merge conflict in your local ZTK
 checkout.  E.g., from [1]:


 An internal error occured due to a bug in either zc.buildout or in a
 recipe being used:
 Traceback (most recent call last):
   File 
 /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 
 1659, in main
 user_defaults, windows_restart, command)
   File 
 /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 
 182, in __init__
 data['buildout'].copy(), override))
   File 
 /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 
 1333, in _open
 eresult = _open(base, extends.pop(0), seen, dl_options, override)
   File 
 /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, line 
 1313, in _open
 parser.readfp(fp)
   File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 305, in 
 readfp
 self._read(fp, filename)
   File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 510, in 
 _read
 raise e
 ParsingError: File contains parsing errors: 
 /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg
 [line 206]: ' .mine\n'
 [line 278]: '===\n'
 [line 350]: ' .r111557\n'
 Seems like you had local, uncommitted changes there, which kind of hurts
 our ability to reproduce failures elsewhere.
 
 Ok there is something wrong, I'll clean eveything
 
 Before the buildout, I'm doing a
 sed -i s/svn+ssh/svn/ ztk.cfg zopeapp.cfg
 because the buildbot is not supposed to have a ssh key.
 Then I'm doing a svn revert of these two files.
 But if the buildout fails, the revert is not done.

I've recreated the slave, then reordered the commands. It should be better.

Yesterday there was a single failure on zope.app.container because of 
dublincore 
permissions.  Today there are another one on the apidoc.

Christophe


 
 Is there another way to disable ssh?
 
 
 
 [1]http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.4%20Linux%2032bit/builds/61/steps/bootstrap/logs/stdio


 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkvZkPoACgkQ+gerLs4ltQ5GPACfV0/JsnOJj8t/axiii8OcJ1Hv
 yusAoILNm4Y1oYa9UTJ2Yy2s9xYWdxyt
 =xNdK
 -END PGP SIGNATURE-

 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )


 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 10 OK, 6 Failed

2010-04-29 Thread Christophe Combelles
Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Zope Tests Summarizer wrote:
 
 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:24 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html

 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Wed Apr 28 23:00:25 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html
 
 Christophe,
 
 These failures appear to be due to a merge conflict in your local ZTK
 checkout.  E.g., from [1]:
 
 
 An internal error occured due to a bug in either zc.buildout or in a
 recipe being used:
 Traceback (most recent call last):
   File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, 
 line 1659, in main
 user_defaults, windows_restart, command)
   File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, 
 line 182, in __init__
 data['buildout'].copy(), override))
   File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, 
 line 1333, in _open
 eresult = _open(base, extends.pop(0), seen, dl_options, override)
   File /tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py, 
 line 1313, in _open
 parser.readfp(fp)
   File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 305, in 
 readfp
 self._read(fp, filename)
   File /usr/local/Python2.6.4/lib/python2.6/ConfigParser.py, line 510, in 
 _read
 raise e
 ParsingError: File contains parsing errors: 
 /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg
  [line 206]: ' .mine\n'
  [line 278]: '===\n'
  [line 350]: ' .r111557\n'
 
 Seems like you had local, uncommitted changes there, which kind of hurts
 our ability to reproduce failures elsewhere.

Ok there is something wrong, I'll clean eveything

Before the buildout, I'm doing a
sed -i s/svn+ssh/svn/ ztk.cfg zopeapp.cfg
because the buildbot is not supposed to have a ssh key.
Then I'm doing a svn revert of these two files.
But if the buildout fails, the revert is not done.

Is there another way to disable ssh?



 
 [1]http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.4%20Linux%2032bit/builds/61/steps/bootstrap/logs/stdio
 
 
 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iEYEARECAAYFAkvZkPoACgkQ+gerLs4ltQ5GPACfV0/JsnOJj8t/axiii8OcJ1Hv
 yusAoILNm4Y1oYa9UTJ2Yy2s9xYWdxyt
 =xNdK
 -END PGP SIGNATURE-
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope Tests: 10 OK, 6 Failed

2010-04-26 Thread Christophe Combelles
Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Zope Tests Summarizer wrote:
 
 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Apr 25 23:13:57 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014124.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Apr 25 23:14:06 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014125.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit
 From: ccomb at free.fr
 Date: Sun Apr 25 23:14:08 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014126.html
 
 These failures are a result of having the ztk.cfg pin dependencies:
 zope.testbrowser trunk now depends on mechanize=0.2.0, and no longer on
 Clientform at all.
 
 I'm not sure how to fix this, as there is no release (yet) of
 zope.testbrowser with these dependencies.

h, I'm wondering too... Maybe like this:

If the next version of zope.testbrowser is to be part of the ZTK 1.0, we just 
have to change the version of mechanize in ztk.cfg to be 0.2.0.
However if the next version of zope.testbrowser is a major version that won't 
be 
part of ZTK 1.0 (but 1.1 instead), we should create a maintenance branch for 
the 
latest current release of zope.testbrowser, and let ztk.cfg point to this 
branch 
instead of the trunk.

Christophe

 
 
 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iEYEARECAAYFAkvVhRkACgkQ+gerLs4ltQ7KNQCgmRULf784bf3t/IdXq+OoqnOU
 xEYAoNdJ8x7w7pzgZrPdNzTW9jR30jhm
 =N1dV
 -END PGP SIGNATURE-
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] ZTK community packages

2010-04-25 Thread Christophe Combelles
Hi!

I believe packages such as z3c.form, z3c.macro, z3c.template, z3c.pagelet (and 
many others) are among the most important packages. I wonder why they are not 
included in the ZTK? I always end up using them, I believe they should even be 
part of the core ZTK.

If they are not part of the core, I would like them to be part of a 
*community.cfg* list. There already is a community.cfg list in BlueBream, but I 
don't like having many foobartoolkit in the wild, with many package lists to 
maintain. It's already difficult enough to maintain just 1 list for the 
zopetoolkit. Let's focus on it.

regards,
Christophe

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZTK community packages

2010-04-25 Thread Christophe Combelles
Hanno Schlichting a écrit :
 Hi.
 
 On Sun, Apr 25, 2010 at 11:14 AM, Christophe Combelles cc...@free.fr wrote:
 I believe packages such as z3c.form, z3c.macro, z3c.template, z3c.pagelet 
 (and
 many others) are among the most important packages. I wonder why they are not
 included in the ZTK? I always end up using them, I believe they should even 
 be
 part of the core ZTK.
 
 We have written down some definition of what constitues a core library
 at http://docs.zope.org/zopetoolkit/about/coreextra.html. That
 document is outdated to some degree, and likely the steering group
 should now be replaced by the release team.

I understand the principle of extra packages. They are not part of the core, 
but they use the core, and they may be part of the core in the future.
That's a good thing, but looking at the zopetoolkit package, there is no such 
list yet. I really think we should track such packages in an extra.cfg file.

I think it has some advantages for everyone:

For the extra packages:

- they can benefit from the buildbot infrastructure
- it increases their visibility
- it encourages their maintainers to support and release new versions
- they can more easily find a place in the large version set of all packages

For the core:

- it gives an easy access to many more third-party tests that can help find 
bugs 
in the ztk core or improve it.
- it helps selecting future candidates for inclusion in the core

 
 Nevertheless the criteria given in that document are still sensible in
 my opinion. z3c.form might at some point become part of the ZTK. But
 right now none of the major projects includes it in its core. The

Regarding z3c.form, it will be at least part of Plone, via the Dexterity 
content 
type library. And I suppose that many zope 3 projects are using it.


 other z3c libraries you mention, I have never heard of or wouldn't
 know what they did. They sound to me related to a specific way of
 constructing user interface related code. I think there's many
 different approaches to that and only very few can claim to be used by
 multiple of the major projects.

z3c.pagelet is the best way I've seen to create really redistributable browser 
page templates, because they are not linked to any macro or master template. 
They basically are both browser pages and content providers, and they can 
choose 
themselves their content template and layout template from bottom up. Among 
other advantages, they benefit from the 2-way update/render pattern of the 
content providers or viewlets.

z3c.macro is an easy way to register macros in zcml, then use it with 
use-macro=macro:somemacro without the burden of creating a view dedicated to 
macro retrieval.

z3c.template can make content templates and layout templates context-dependent. 
They are registered separately from the views.

Not mentionning z3c.formjs, which is a good jquery-based library on top of 
z3c.form to create javascript-enabled forms.

 
 If they are not part of the core, I would like them to be part of a
 *community.cfg* list. There already is a community.cfg list in BlueBream, 
 but I
 don't like having many foobartoolkit in the wild, with many package lists to
 maintain. It's already difficult enough to maintain just 1 list for the
 zopetoolkit. Let's focus on it.
 
 What you are describing is similar to the idea of the extra concept
 we have defined for the ZTK. It has at this stage no manifestation in
 any code, version list or process around it.

Ah ok, if this is already defined, but just missing an implementation, I will 
help with implementing it.

 
 At this stage I would prefer to focus on the ZTK as a
 least-common-denominator of the major projects. And only if we are
 actually able to agree on such a set, should we try to extend it. This
 is going to be hard enough and extending the set of packages won't
 make it any easier.

Sure, it should not block or even delay the ZTK release. We can even release a 
ZTK with failing tests on the extra packages. I'm confident that these failures 
will be fixed much quicker in they are visible to everyone ;)

Christophe

 
 That doesn't mean you shouldn't go forward with your idea. I just like
 to have it separate from the ZTK.
 
 Hanno
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] buildbot for the KGS 3.4.1

2010-04-24 Thread Christophe Combelles
Here is one (only linux 32bits)

http://buildbot.afpy.org/kgs3.4.1/waterfall
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Circular dependency hell.

2010-04-18 Thread Christophe Combelles
Tres Seaver a écrit :
 So far the main circularity was that everything depended on
 zope.testing as a testrunner, zc.buildout for making the development
 environment, and zope.testing obviously depended on zope.interface
 etc. I solved that by also adding support for setuptools/distributes
 testrunner and using that instead. That fixed zope.interface,
 zope.event and zope.exception. These modules still have buildout
 configurations if you want them, but you don't need buildout anymore.
 zope.interface, zope.event and zope.exception can now be developed and
 tested with only setuptools, you can run the tests with python
 setup.py test both under Python 2 and 3.
 
 Yay!  That is a big win -- I'd like to see us automate testing this way,
 so that future development doesn't erode it.  Developing ZTK packages
 using buildout should be a convenience, not a mandate.

Depending on setuptools for tests in another evil thing. We should not assume a 
*setup* tool to be a testrunner, and we should not depend on the behaviour of 
setuptools to write tests. Setuptools is already doing too many things and 
Tarek 
is taking care (with distutils2 and distribute) to cleany separate the 
functionalities, such as installing, distributing, etc.

Testing is not related to configuring nor installing, and python setup.py 
test 
is no more meaningful than python setup.py makethecoffee.

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Repository for the zope mail summarizer

2010-04-18 Thread Christophe Combelles
Patrick Gerken a écrit :
 Hi,
 
 I wanted to look into the script that summarizes the mails sent to zope-test.
 The best code I found is this
 http://cvs.zope.org/Packages/TestScripts/
 but I suspect that there are newer versions, I just don't know where.
 I'd like modifiy the script to understand status mails from buildbots too.

That would be a good thing! I had to add specific code to reformat the subject 
line in the master.cfg. If it can help you can have a look at them here:

http://buildbot.afpy.org/ztk1.0dev/master.cfg
http://buildbot.afpy.org/bluebream/master.cfg

This is in the message_formatter function.

Christophe


 Anybody knows where the latest version of this code is?
 And who runs that script atm?
 
 Best regards,
 
 Patrick
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Circular dependency hell.

2010-04-18 Thread Christophe Combelles
Lennart Regebro a écrit :
 On Sun, Apr 18, 2010 at 10:37, Christophe Combelles cc...@free.fr wrote:
 Depending on setuptools for tests in another evil thing. We should not 
 assume a
 *setup* tool to be a testrunner, and we should not depend on the behaviour of
 setuptools to write tests.
 
 I'm not sure what you mean there, setuptools doesn't behave in any
 particular way when running tests.

ok, not a lot, there is currently one single particular behaviour, which is 
adding tests from the result of the additional_tests function in a module.
That probably won't hurt.


 
 Setuptools is already doing too many things and Tarek
 is taking care (with distutils2 and distribute) to cleany separate the
 functionalities, such as installing, distributing, etc.
 
 Yes, but that work is not done yet. And one thing that's needed to be
 able to run the tests under Python 3 is  building it. So it's hard to
 separate the building and the running of testsm as a Python 3 capable
 testrunner would need to run setup.py build first anyway. Which means
 you depends on setuptools/distribute whichever way you turn.
 
 Testing is not related to configuring nor installing, and python setup.py 
 test
 is no more meaningful than python setup.py makethecoffee.
 
 It might seem so, but it is unfortunately not true when considering Python 3.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] KGS 3.4.1 versions

2010-04-17 Thread Christophe Combelles
Christophe Combelles a écrit :
 Roger a écrit :
 Hi 

 Betreff: Re: [Zope-dev] KGS 3.4.1 versions

 Adam GROSZER a écrit :
 Hello,

 There is a sheet with versions for KGS 3.4.1 

 http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=
 html

 Anyone for/against those versions?

 The open questions that remain:
 * What about pytz 2010g?
 * Which lxml version to take? 1.3.6?
 * What about zope.app.container 3.6.2?
 * Would be nice to have zope.testbrowser 3.5.1

 Comments are welcome.

 z3c.layer has a major security issue, because of trusted 
 traversing adapters that removes the security proxy 
 everywhere. 
 yes and no, only miss use could end in security issues
 It's not really a security issue, it's the only concept which allows
 to use nested sites with more then one IAuthentication utility
 and allows to authenticate on objects behind the first site.

 But since this was such a rare use case, we decided to split
 the package in different packages which also supports a non
 trusted setup. This makes the packages more general usable
 without to run into security issues based on trusted
 confirgurations where non trusted is needed.

 This package has been retired and splitted into 
 its 3 subpackages :

 z3c.layer.minimal
 z3c.layer.pagelet
 Both package above should not use trusted traverser

 z3c.layer.trusted
 This package should still use trusted traverser

 There is no problem upgrading to branch 1.0 of these 
 packages, as they don't have any significant changes, 
 excepted the splitting. However:

 z3c.layer.pagelet should be in version 1.0.2. Nothing below.
 z3c.layer.minimal has no corrected 1.0 branch. A new 
 maintenance release 1.0.2 of this package should be released.
 z3c.layer.trusted is OK, since this is trusted in purpose. (I think)
 Yes
 
 
 Ok thanks, I'll release z3c.layer.minimal during the WE.


I've released z3c.layer.minimal 1.0.2 with the fix,
and z3c.layer 0.2.4 with the same fix.

For the KGS 3.4.1, we just have to upgrade z3c.layer to 0.2.4.
No need to add z3c.layer.[pagelet|minimal|trusted]

Christophe



 
 
 
 Regards
 Roger Ineichen

 Christophe
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  ** (Related lists -  
 https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )



 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] KGS 3.4.1 versions

2010-04-16 Thread Christophe Combelles
Roger a écrit :
 Hi 
 
 Betreff: Re: [Zope-dev] KGS 3.4.1 versions

 Adam GROSZER a écrit :
 Hello,

 There is a sheet with versions for KGS 3.4.1 

 http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=
 html

 Anyone for/against those versions?

 The open questions that remain:
 * What about pytz 2010g?
 * Which lxml version to take? 1.3.6?
 * What about zope.app.container 3.6.2?
 * Would be nice to have zope.testbrowser 3.5.1

 Comments are welcome.

 z3c.layer has a major security issue, because of trusted 
 traversing adapters that removes the security proxy 
 everywhere. 
 
 yes and no, only miss use could end in security issues
 It's not really a security issue, it's the only concept which allows
 to use nested sites with more then one IAuthentication utility
 and allows to authenticate on objects behind the first site.
 
 But since this was such a rare use case, we decided to split
 the package in different packages which also supports a non
 trusted setup. This makes the packages more general usable
 without to run into security issues based on trusted
 confirgurations where non trusted is needed.
 
 This package has been retired and splitted into 
 its 3 subpackages :

 z3c.layer.minimal
 z3c.layer.pagelet
 
 Both package above should not use trusted traverser
 
 z3c.layer.trusted
 
 This package should still use trusted traverser
 
 There is no problem upgrading to branch 1.0 of these 
 packages, as they don't have any significant changes, 
 excepted the splitting. However:

 z3c.layer.pagelet should be in version 1.0.2. Nothing below.
 z3c.layer.minimal has no corrected 1.0 branch. A new 
 maintenance release 1.0.2 of this package should be released.
 z3c.layer.trusted is OK, since this is trusted in purpose. (I think)
 
 Yes


Ok thanks, I'll release z3c.layer.minimal during the WE.



 
 Regards
 Roger Ineichen
 
 Christophe
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  ** (Related lists -  
 https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

 
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] KGS 3.4.1 versions

2010-04-15 Thread Christophe Combelles
Adam GROSZER a écrit :
 Hello,
 
 There is a sheet with versions for KGS 3.4.1
 http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=html
 
 Anyone for/against those versions?
 
 The open questions that remain:
 * What about pytz 2010g?
 * Which lxml version to take? 1.3.6?
 * What about zope.app.container 3.6.2?
 * Would be nice to have zope.testbrowser 3.5.1
 
 Comments are welcome.
 

z3c.layer has a major security issue, because of trusted traversing adapters 
that removes the security proxy everywhere. This package has been retired and 
splitted into its 3 subpackages :

z3c.layer.minimal
z3c.layer.pagelet
z3c.layer.trusted

There is no problem upgrading to branch 1.0 of these packages, as they don't 
have any significant changes, excepted the splitting. However:

z3c.layer.pagelet should be in version 1.0.2. Nothing below.
z3c.layer.minimal has no corrected 1.0 branch. A new maintenance release 1.0.2 
of this package should be released.
z3c.layer.trusted is OK, since this is trusted in purpose. (I think)

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Minutes from this weeks meeting

2010-04-15 Thread Christophe Combelles
Christian Theune a écrit :
 Hi,

Hi thanks for the minutes!
 
 here's the minutes. As I've been adventurous, I'll add a few comments:
 
 * I've started diving into the matter of how to manage items that we
   park/defer/postpone/wait for and thus started using an online system.
   (The only one I was able to find anyway.)

which online system are you talking about?


 
 * The output is a PDF which is currently a bit messy as I wanted to get
   rid of my text files that had the open issues sitting in there and
   thus had to add all of them to our agenda on Tuesday and then defer
   them. I think next week will become less noisy.
 
 * In general I can give access to stuff there to more people. I'll
   probably add those of you that step up for some tasks so I can mark
   the assignments appropriately.
 
 I hope this helps, at least I have the feeling it helps me stay 
 organized and thus take less time in the future to write up the agendas 
 and minutes.
 
 Christian
 
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Incoming buildbots alerts for ZTK 1.0dev and Bluebream

2010-04-10 Thread Christophe Combelles
Hi,

The afpy buildbots are now enough stable and I've now configured email alerts 
to 
the zope-tests list.

The two buildbots are :
- ZTK 1.0 dev
- BlueBream template

http://buildbot.afpy.org/

The definition of the ZTK 1.0dev is:

all the development branches of the packages in the ZTK 1.0, as defined in 
the 
buildout of the zopetoolkit package. Currently they all point to the package 
trunks, but as soon as the ZTK 1.0 will be released, they should point to the 
maintenance branches.

Christophe

PS : I've seen that /tmp is filled with a LOT of tmp folders, so there is 
something wrong with tests somewhere.
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Wanted: representatives from Zope 2, grok, and BlueBream to engineer ZTK 1.0 release

2010-04-03 Thread Christophe Combelles
Christian Theune a écrit :
 Hi everyone,
 
 on the way towards a ZTK 1.0 release we first looked for a single 
 volunteer release manager who would drive the process.
 
 As no one stepped up and no (serious) nominations were presented the 
 discussion went back to the drawing board and the plan was changed a 
 bit: we'd like to go with a (small) team of representatives from the 
 large ZTK consumers, namely: Zope 2, grok, and BlueBream.
 
 I assume at least someone from every project is listening here, so I 
 suggest the following:
 
 * grok and BlueBream: please check within your own sub-communities for
someone you'd like to represent you in the draft of what the ZTK 1.0
should look like and who is willing to help with it.

Hi!

I will be the representative for BlueBream, since Baiju is already doing an 
enormous amount of work and he needs help.

Let's wait a little bit more for a caveman to stand up for Grok, and we can 
start discussing about the release of the ZTK 1.0.
This should probably happen soon, because Grok 1.1 and BB 1.0 are currently 
using the same versions and are about to be released.


Christophe


 
 * Zope 2: In theory I'd suggest the Zope 2 release manager. In practice
I'd like to nominate Hanno because he's been very active with Zope 2
recently and already has done work on the ZTK before. (Hanno: sorry.
*duck*)
 
 We don't have a complete set of tasks/issues for the release yet, 
 however, here's a few:
 
 * Find a definition of 'ZTK release' that fits all consumers
 * Establish actual task list and work on it
 * Ensure we have windows binaries
 
 We don't have a schedule to follow, but I think we can get started 
 within the next weeks (read that as soon as we have the staffing issues 
 out of the way).
 
 Cheers,
 Christian
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] RFC: 3.4.1 KGS?

2010-03-31 Thread Christophe Combelles
Hi,

Marius Gedminas a écrit :
 On Wed, Mar 31, 2010 at 01:37:47PM +0200, Christian Theune wrote:
 On 03/31/2010 12:35 PM, Adam GROSZER wrote:
 One point for the next agenda:
 As Marius also had the issue to do a KGS 3.4.1.
 
 Mostly I wanted to know if anybody was using the KGS in production and
 interested in a point release.


I do

I'm already using all the minor versions upgrades, this is also some kind of 
unreleased 3.4.1.


 
 So, my plan of action is:
 
  * fix zope.sendmail using the approach discussed on this list a few
weeks ago
 
  * look at other possible bugfix upgrades, see if there are any
important bugs fixed (zope.release's bin/list-latest is useful here)


It would be good to have a tool (bin/upgrade-minor or something) to upgrade 
package versions of a buildout to the highest minor release available. I 
remember that bin/list-latest only works for the  Maybe it already exists?


 
  * bump ZODB3, zope.sendmail, zope.security versions in the 3.4 KGS, see
what buildbot things of this
 
  * try to get a 3.4.1 release out of the door -- this is where I'm
fuzzy.  I think I used to have ssh access to download.zope.org, but I
don't even remember how you're supposed to use zope.release's bin/upload,
and I never knew how the releases were made.


I had helped a bit for the 3.4.0 release, I still remember a few things, 
particularly about zope.release or zope.kgs. However I did'nt have any ssh 
access. But I can probably help.

Christophe


 
 Marius Gedminas



___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Another buildbot with the package trunks of the ZTK

2010-03-07 Thread Christophe Combelles
I've added another buildbot that runs the ZTK tests against all the package 
trunks: http://buildbot.afpy.org
This should allow to detect breakages earlier (before releasing packages) on 
the 
different versions of Python.

The Python 3.1 slave is just there to remind us there's another task waiting ;)

Christophe

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Summary of today's developer meeting

2010-03-03 Thread Christophe Combelles
Thanks for the summary!

  The current state of nightly builds is a bit untidy. According to
  http://docs.zope.org/zopetoolkit/process/buildbots.html there's four buildbot
  installations with various scopes. The last two in this listing are currently
  non-functional.

The third one is online again
http://zope3.afpy.org/buildbot/

Christophe


Christian Theune a écrit :
 Hi,
 
 here's my first shot at a summary of today's meeting. I found the
 meeting itself very positive and energetic - thanks again to everyone
 who joined.
 
 If anyone knows another good place to announce this summary (we should
 be more visible to the outside world!), please feel free to post them
 (or link to them) somewhere and maybe tell me for the future.
 
 Cheers,
 Christian
 
 
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Legal formalities to accept log and design

2010-01-24 Thread Christophe Combelles
Jens Vagelpohl a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 1/24/10 13:08 , Baiju M wrote:
 Hi,
 I would like to know the legal formalities required
 to accept a logo (with special font).
 Also I would like to know the same for web design.

 Is there any guideline for Zope Foundation ?

 BlueBream team want to use a logo designed by an external person:
 http://muthukadan.net/bluebream/bluebream-logo-v1.png
 The font used there (Perizia: http://fedoraproject.org/wiki/Perizia_fonts) is
 designed by the same designer and released under GPL.

 One of my friend has offered a web design for the site (not done yet).
 
 All that's perfectly fine. As Andreas said, there are no guildelines, as
 long as you are not using material that's already trademarked and
 copyrighted.

maybe just be sure the original author won't claim anything in the future?
ie. the logo should be released with a free licence. Just to avoid the kind of 
troubles we had with new.zope.org

 
 Using a GPL font for the logo surely won't force us to abandon the ZPL,
 no reason for concern there. The logo is nice, by the way.
 
 One thing to note: While you or the designer work on the logo, make sure
 you have a few vector graphics like EPS files as well, those will look
 the nicest if someone wants to use the logo in a printed publication.


I'd personally prefer to see an SVG file. I can create a clean one from the 
bitmap logo if needed. It should then be stored in the bluebream template svn.

Baiju, when are we going to be sure we can use this logo? (in blog articles, or 
any publication). I also find it nice.


 
 jens
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.8 (Darwin)
 
 iEYEARECAAYFAktcSfsACgkQRAx5nvEhZLIRUgCeLmXoL0HF3Z7Z3cxThwfYekI4
 yKgAniozfiXtQAZx9adV4vl/YTkPwM+O
 =7RFM
 -END PGP SIGNATURE-
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] z3c.sqlalchemy 1.0.11

2009-12-10 Thread Christophe Combelles
Hi,

There is no tag for z3c.sqlalchemy 1.0.11

http://svn.zope.org/z3c.sqlalchemy/tags/?rev=106375

and the latest package on PyPI is 1.0.12. No other earlier versions.


We have an application in production with z3c.sqlalchemy 1.0.11. I don't know 
how the paquage we use was generated, but we needed to regenerate it,
and we found that the revision for 1.0.11 is r78477

May I commit a tag for this version?

It would also be good that earlier packages be generated and uploaded to PyPI. 
I 
can do it if someone gives me admin access to it.

regards,
Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.sqlalchemy 1.0.11

2009-12-10 Thread Christophe Combelles
Andreas Jung a écrit :
 Am 10.12.09 13:34, schrieb Christophe Combelles:
 Hi,

 There is no tag for z3c.sqlalchemy 1.0.11

 http://svn.zope.org/z3c.sqlalchemy/tags/?rev=106375

 and the latest package on PyPI is 1.0.12. No other earlier versions.


 We have an application in production with z3c.sqlalchemy 1.0.11. 
 
 1.0.12 likely only a minor bugfix release. So go with this version.


We had actually no problem regenerating a package from the revision 
corresponding to 1.0.11;  but our problem is to be able to regenerate a 
buildout 
identical to what we have in production (ie with 1.0.11), with packages from 
PyPI.  Version 1.0.11 is mentionned in the changelog, but does not exist 
anywhere today.
We've done it with our internal PyPI mirror, but someone else might want to use 
any version prior to 1.0.12, for example to reproduce some specific problem.

is it a problem to create a tag, and upload packages?


 
 -aj

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Baiju's book on ZCA

2009-12-09 Thread Christophe Combelles
Hi all !

I've finished translating Baiju's book into french (A Comprehensive Guide to 
Zope Component Architecture).

The bzr branch is here:
https://code.launchpad.net/~ccomb/zcadoc/book-fr

I've also generated some HTML and PDF output:
http://ccomb.gorfou.fr/static/zcadoc/zca-fr.pdf
http://ccomb.gorfou.fr/static/zcadoc/zca-fr.html


The english version needs more contributions, it has not been updated for a few 
months and some new chapters are not finished. It would be great that some 
volonteers help reviewing and completing this book.

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Tests results for Zope 3.5dev KGS

2009-02-09 Thread Christophe Combelles
Stephan Richter a écrit :
 On Sunday 08 February 2009, Christophe Combelles wrote:
 For now I only have the py2.5-64bit slave, but I have similar results,
 though less tests:

 http://zope3.afpy.org/buildbot/
 12895 tests, 27 failures, 10 errors

 I'll add other slaves soon (32bit and py2.6).
 
 Fantastic! That's great news. BTW, I think you can take Py3.0 from the list, 
 since we are not aiming at supporting it yet.

It doesn't eat any time or CPU since it doesn't work, so I'll leave it here, 
think of it as some sort of reminder :)  As soon as we'll have virtualenv, 
buildout and setuptools released for 3.0, we will have a first sight on the 
global status on this topic.

Christophe
(working on setting up a 32bit slave, either on qemu or another machine)

 
 I think several problems are shallow:
 
 - Restricted Python fails for strange reasons. Installing the trunk as devel 
 egg works. I think it has something to do with Sidnei making the latest 
 release and he is on Windows.
 
 - The z3c.form issues should be fixed in trunk. Anyone, how close are we to a 
 z3c.form 2.0 release? (Mmmh, I guess I should know. ;-( Adam? Roger? Dan? 
 Malthe?)
 
 - Several other packages fail because they have not been adjusted to the 
 latest refactorings.
 
 Those are the low-hanging fruits I think.
 
 Regards,
 Stephan

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Tests results for Zope 3.5dev KGS

2009-02-08 Thread Christophe Combelles
For now I only have the py2.5-64bit slave, but I have similar results, though 
less tests:

http://zope3.afpy.org/buildbot/
12895 tests, 27 failures, 10 errors

I'll add other slaves soon (32bit and py2.6).

Christophe

Stephan Richter a écrit :
 Hi all,
 
 I just ran all tests over night and here is the result
 
 Tests with errors:
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
testDoomedTransaction 
 (zope.app.publication.tests.test_zopepublication.ZopePublicationTests)
testTransactionAnnotation 
 (zope.app.publication.tests.test_zopepublication.ZopePublicationTests)
testTransactionCommitAfterCall 
 (zope.app.publication.tests.test_zopepublication.ZopePublicationTests)
testAbortTransactionWithErrorReportingUtility 
 (zope.app.publication.tests.test_zopepublication.ZopePublicationErrorHandling)
 
 Tests with failures:

 /opt/zope/packages/eggs/ZODB3-3.9.0a10-py2.5-linux-i686.egg/ZEO/tests/zeo_blob_cache.test

 /opt/zope/packages/eggs/z3c.etestbrowser-1.2.1-py2.5.egg/z3c/etestbrowser/README.txt

 /opt/zope/packages/eggs/z3c.layer.minimal-1.0.1-py2.5.egg/z3c/layer/minimal/tests/../README.txt

 /opt/zope/packages/eggs/zope.app.testing-3.6.0-py2.5.egg/zope/app/testing/cookieTestOne.txt

 /opt/zope/packages/eggs/zope.app.testing-3.6.0-py2.5.egg/zope/app/testing/cookieTestTwo.txt
/opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/contenttype.txt
/opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/download.txt
/opt/zope/packages/eggs/zope.file-0.4.0-py2.5.egg/zope/file/upload.txt
/opt/zope/packages/eggs/zope.html-1.1.0-py2.5.egg/zope/html/browser.txt
/opt/zope/packages/eggs/z3c.form-1.9.0-py2.5.egg/z3c/form/tests/../form.txt

 /opt/zope/packages/eggs/z3c.form-1.9.0-py2.5.egg/z3c/form/tests/../group.txt

 /opt/zope/packages/eggs/z3c.formjs-0.4.1-py2.5.egg/z3c/formjs/tests/../jsclientevent.txt

 /opt/zope/packages/eggs/zc.catalog-1.3.0-py2.5.egg/zc/catalog/extentcatalog.txt

 /opt/zope/packages/eggs/zc.catalog-1.3.0-py2.5.egg/zc/catalog/extentcatalog.txt
normalize (zc.i18n.date)
/opt/zope/packages/eggs/zc.table-0.7.0-py2.5.egg/zc/table/column.txt
/opt/zope/packages/eggs/zc.table-0.7.0-py2.5.egg/zc/table/fieldcolumn.txt
test_ctl (zc.zope3recipes.tests)
test_sane_errors_from_recipe (zc.zope3recipes.tests)
work_with_old_zc_deployment (zc.zope3recipes.tests)

 /opt/zope/packages/eggs/zc.zope3recipes-0.7.0-py2.5.egg/zc/zope3recipes/README.txt
test_provides 
 (zope.app.interface.tests.test_interface.PersistentInterfaceTest)
test_error_handling (zope.formlib.tests)

 /opt/zope/packages/eggs/zope.schema-3.5.1-py2.5.egg/zope/schema/tests/../validation.txt

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/setupstack.txt

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-debugging-layer-setup.test

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-layers-ntd.txt

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-layers.txt

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-profiling.txt

 /opt/zope/packages/eggs/zope.testing-3.7.1-py2.5.egg/zope/testing/testrunner/testrunner-profiling-cprofiler.txt
 Total: 12937 tests, 30 failures, 10 errors in 41 minutes 1.150 seconds.
 
 Regards,
 Stephan

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope3docs

2009-02-03 Thread Christophe Combelles
Christian Theune a écrit :
 On Mon, 2 Feb 2009 09:16:38 -0800
 Paul Carduner paulcardu...@gmail.com wrote:
 
 On Mon, Feb 2, 2009 at 8:49 AM, Christian Theune c...@gocept.com
 wrote:
 My short-term goal is to produce a document that I can pass to new
 developers with reasonable confidence that they know roughly how to
 move in our community.

 In the long term I'd also like to incorporate documentation about
 Zope 3 components themselve there.
 Awesome!

 I'd be happy to get feedback on this and I'll probably come up with
 some questions if I can't find an answer in the existing documents.
 I'll ask the question of why not put this on the new.zope.org website?
 
 .oO(Geez, we're bad at communicating internally ...)
 
 new.zope.org does not exist anymore. The project was cancelled a while
 ago. We can not use that layout.


there is not much design apart from the css, and a few illustrations. I've 
contributed some textual contents on this site, the folder arrangement, the 
get-started page, a few tutorials in the Example folder. You can retrieve 
everything and move it to the svn as rst files. I think we can keep the same 
kind of folder layout (Get Started, Projects with z2, z3 app, z3 library, zodb, 
etc.).
Since the new site is not intended to be a collaborative space, we really don't 
need a Plone for that. A Sphinx is ideal.

Christophe

 
 .oO(Hopefully the communication about this that ended up in my brain
 was correct)
 
 Nevertheless, you're right about the ease of writing ReST in my own
 editor.
 
 Christian
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 3.5dev KGS

2009-02-02 Thread Christophe Combelles
Stephan Richter a écrit :
 Hi everyone,
 
 I have setup a KGS for Zope 3.5, so that people can test the development KGS.
 
 http://download.zope.org/zope3.5/
 
 I have updated all packages to the latest version available. I have not 
 tested 
 anything. I would like someone to setup a buildbot like at
 
 http://zope3.pov.lt/buildbot/

Ok, Sebastien and I are going to setup the buildbot, we have a dedicated server 
for that.

Marius, could you help us start, by sending me your buildbot configuration?

Christophe

 
 Regards,
 Stephan

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 3.5dev KGS

2009-02-02 Thread Christophe Combelles
Marius Gedminas a écrit :
 On Mon, Feb 02, 2009 at 12:38:07PM +0300, Dan Korostelev wrote:
 2009/2/2 Christophe Combelles cc...@free.fr:
 Stephan Richter a écrit :
 Hi everyone,

 I have setup a KGS for Zope 3.5, so that people can test the development 
 KGS.

 http://download.zope.org/zope3.5/

 I have updated all packages to the latest version available. I have not 
 tested
 anything. I would like someone to setup a buildbot like at

 http://zope3.pov.lt/buildbot/
 Ok, Sebastien and I are going to setup the buildbot, we have a dedicated 
 server
 for that.

 Marius, could you help us start, by sending me your buildbot configuration?
 It's even better to have the buildbot configuration published so
 people could easily setup their copies :)
 
 Here it is, again, to keep the discussion nicely self-contained in list
 archives:
 
   http://zope3.pov.lt/master.cfg
 
 Since 3.4 is probably not going to change much now that it's released
 (though it would be nice to fix the remaining persistent build failures
 on 32-bit buildslaves), I can probably just switch
 
   http://zope3.pov.lt/buildbot/
 
 to run against the 3.5 KGS.

We need to maintain this branch and probably release some 3.4.1 bugfix, so we 
still need the buildbot for this branch.
The buildbot for KGS 3.5 also need to run tests with python 2.6.
Maybe you can switch your buildbot to run a 3.4.1dev KGS?

Christophe

 
 BTW, it would be great to have buildbot for python 2.6, if we want to
 support it in 3.5. It was somewhat problematic for zope3.pov.lt, as
 there's old ubuntu versions on that servers, but if you are going to
 setup another one - may be you'll get py2.6 for that? ;-)
 
 Windows build slaves would also be very nice to have, if anybody has
 Windows and can spare the pain to figure out how to baby-sit it.
 
 Marius Gedminas
 
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 3.5dev KGS

2009-02-02 Thread Christophe Combelles
Dan Korostelev a écrit :
 2009/2/2 Christophe Combelles cc...@free.fr:
 Stephan Richter a écrit :
 Hi everyone,

 I have setup a KGS for Zope 3.5, so that people can test the development 
 KGS.

 http://download.zope.org/zope3.5/

 I have updated all packages to the latest version available. I have not 
 tested
 anything. I would like someone to setup a buildbot like at

 http://zope3.pov.lt/buildbot/
 Ok, Sebastien and I are going to setup the buildbot, we have a dedicated 
 server
 for that.

 Marius, could you help us start, by sending me your buildbot configuration?
 
 It's even better to have the buildbot configuration published so
 people could easily setup their copies :)
 
 BTW, it would be great to have buildbot for python 2.6, if we want to
 support it in 3.5. It was somewhat problematic for zope3.pov.lt, as
 there's old ubuntu versions on that servers, but if you are going to
 setup another one - may be you'll get py2.6 for that? ;-)

Sure, we plan to support 2.4, 2.5, 2.6 in 32 and 64bit. Probably even 3.0 as 
soon as there is something working for that version. Lennart has already 
started 
porting setuptools.

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] snakebite

2009-02-01 Thread Christophe Combelles
Sebastien Douche a écrit :
 On Sat, Jan 31, 2009 at 11:55, Martijn Faassen faas...@startifact.com wrote:
 I think the Zope project counts as a prominent Python project and we
 have a lot of interesting code to test, so perhaps they'll let us in. :)

 Would people be interested in working on making use of this platform? We
 could use it for testing of a wide range of packages. Perhaps the ZODB
 would be an interesting package to start with. If so we should approach
 snakebite to see whether we can get on board.
 
 
 Me and Cristophe Combelles (ccomb) are ok to integrate the KGS team.
 And we have alternates solutions if Snakebite reject Zope3 :
 - AFPy (french python association) get a new server
 - My company accept to help Zope project with a (non)dedicated server


I'm really excited to see the Zope 3.4.0 release. Thanks, Stephan!
It's also good to have a 6-month release cycle. But we will need to stabilize 
the KGS very quickly. It'd be nice to let the KGS be built automatically by 
testing each new package version against every other packages.

As Sebastien said, we have (at least) one new machine that can possibly be 
dedicated to set-up a buildbot, in case we can't rely on snakebite. We'll 
probably need help also from Marius who already did this for 3.4 ( 
http://zope3.pov.lt )

Christophe

 
 
 Cheers
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Bug in zope.app.generations fixed and logging increased. Release?

2008-11-26 Thread Christophe Combelles
Christian Theune a écrit :
 Hi,
 
 I've fixed a bug in zope.app.generations and added more logging. Can
 someone have a look on this with a second pair of eyes and give me a go
 for releasing that code as 3.4.2?


Is there something we can do for https://bugs.launchpad.net/zope3/+bug/241416 ?

Christophe


 
 Christian
 
 
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] z3c.table : upcoming release

2008-10-11 Thread Christophe Combelles
Roger Ineichen a écrit :
 Hi Christophe
 
 Betreff: [Zope-dev] z3c.table : upcoming release

 Hi,

 I would like to tag and release z3c.table version 0.6.0, it 
 has important bugfixes, and a few new features over 0.5.0.

 Please tell if someone wants to add more contributions on 
 this package before I do it. It would also be a good idea, 
 for people using this package, to try the trunk with their 
 application and review the fix for advanced batching ( 
 http://zope3.pov.lt/trac/changeset/92028 )

 I've extracted the advanced batching code in a separate 
 function, and I believe it could be moved to z3c.batching?
 
 yes, why not, sounds good to me.
 
 I just added my latest pending bugfix to z3c.table.
 
 I also added you as an Owner to the z3c.batching package at PyPi.


thanks, I will also release z3c.batching 1.1.0 then. I've seen the only 
difference between 1.0.0 and 1.0.1 is a change in the test, but the fix itself 
seems forgotten, so the tests fail.

Christophe

 
 Regards
 Roger Ineichen
 
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] z3c.table : upcoming release

2008-10-10 Thread Christophe Combelles
Hi,

I would like to tag and release z3c.table version 0.6.0, it has important 
bugfixes, and a few new features over 0.5.0.

Please tell if someone wants to add more contributions on this package before I 
do it. It would also be a good idea, for people using this package, to try the 
trunk with their application and review the fix for advanced batching
( http://zope3.pov.lt/trac/changeset/92028 )

I've extracted the advanced batching code in a separate function, and I believe 
it could be moved to z3c.batching?

regards,
Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Call for translating z3c.form

2008-09-05 Thread Christophe Combelles
Dan Korostelev a écrit :
 Hello, fellow users and developers of zope components!
 
 I just added support for i18n in z3c.form, so it can be now translated
 to many languages. If you want to contribute to z3c.form
 internationalization, checkout the z3c.form.pot file from the
 z3c.form's trunk and translate it to your language, then send back to
 me or commit to the repo, if you are a committer.
 
 Thanks!

the french translation is commited!

thanks for the i18n support!

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZODB3 3.9.0-dev-r77011 egg?!

2008-08-19 Thread Christophe Combelles
Chris Withers a écrit :
 Philipp von Weitershausen wrote:
 and why does buildout pick it over a stable release?
 Because buildout, like easy_install, will pick the newest available 
 version for a distribution. Fortunately, buildout has a prefer-stable 
 option so that you can tell it to prefer stable over alpha/beta/dev 
 releases. Also, in any serious situtation you'd want to pin your 
 versions, e.g. using the KGS [2] or a manual list.
 
 Okay, so how come zopeproject doesn't do any of these?
 
 I don't even know how to use the KGS - where would I find docs on that?

Here is a page explaining it:
http://download.zope.org/zope3.4/intro.html

 
 cheers,
 
 Chris
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] bugfix releases for the KGS

2008-08-17 Thread Christophe Combelles
If there are no objections, I would like to tag and release bugfix versions for:

zope.server
zope.publisher
zope.app.server
zc.zope3recipes

They will help to reduce the number of errors in the global test suite for the 
Known Good Set. http://zope3.pov.lt/buildbot/
They at least help in my own setup (py2.4.4 and py2.5.2, Lenny 32bit and Etch 
64 
bit, in a virtualenv, with PIL and enscript installed).

Christophe


PS: z3c.formjs and z3c.formdemo need to be fixed to work with the test buildout 
of the KGS. Can someone help for this?
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] bugfix releases for the KGS

2008-08-17 Thread Christophe Combelles
Stephan Richter a écrit :
 On Sunday 17 August 2008, Christophe Combelles wrote:
 If there are no objections, I would like to tag and release bugfix versions
 for:

 zope.server
 zope.publisher
 zope.app.server
 zc.zope3recipes

 They will help to reduce the number of errors in the global test suite for
 the Known Good Set. http://zope3.pov.lt/buildbot/
 They at least help in my own setup (py2.4.4 and py2.5.2, Lenny 32bit and
 Etch 64 bit, in a virtualenv, with PIL and enscript installed).
 
 +1 None of those packages contain C code, so the release should be easy. My 
 almighty script is running right now to give you access to PyPI and make you 
 all powerful. :-)
 
 Regards,
 Stephan

thanks,
it looks like it's better:

1 failure on z3c.formjs everywhere
1 failure on zdaemon in 64bit
1 failure on ZEO in py2.4/64bit

I can reproduce the failures on zdaemon and ZEO only if I start the py2.4 and 
py2.5 tests at the same time (just like the buildbot).
Interrupting the zdaemon test also makes subsequent tests fail because some 
zdaemon processes are not stopped.

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] KGS buildbot news (zope.server failure almost explained)

2008-08-15 Thread Christophe Combelles
Jens Vagelpohl a écrit :
 On Aug 15, 2008, at 02:35 , Christophe Combelles wrote:
 We should also probably consider waiting a bit more for the new site
 (new.zope.org) to come up, but I don't know when it will be  
 finished. It only
 needs some content for zope2, grok, and some other pages.
 
 I don't see the connection here. The site has nothing to do with these  
 specific issues.

What I mean, is that releasing zope 3.4 along with a new web site is much much 
better than releasing it alone.

 
 jens
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.app.authentication 3.4.3 + download.zope.org/simple == broken

2008-08-14 Thread Christophe Combelles
Gary Poster a écrit :
 If you use the http://download.zope.org/ppix or 
 http://download.zope.org/simple 
   indexes and try to get zope.app.authentication 3.4.3 (the newest),  
 you will get a 404 error.
 
 Looking at PyPI and the zope.org index, it is evident why.
 
 http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists  
 one release, the source release
 
 http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3  
 eggs as well.
 
 I strongly suspect that someone uploaded the zope.app.authentication  
 eggs to PyPI; the zope.org index saw them and recorded them; and then  
 someone removed the eggs from PyPI.
 
 It would be great if someone could re-upload the eggs to PyPI.
 
 More importantly, this is a reminder to please not remove eggs.  The  
 behavior or download.zope.org/simple is reasonable.  Removing eggs  
 isn't. :-)

Indeed...
I've reuploaded them but they don't have the same MD5. Is it a problem? 
easy_install does not seem to complain

 
 Thanks
 
 Gary
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )
 
 

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] KGS buildbot news (zope.server failure almost explained)

2008-08-14 Thread Christophe Combelles
Marius Gedminas a écrit :
 On Sat, Aug 09, 2008 at 01:50:33AM +0300, Marius Gedminas wrote:
 On Sat, Aug 09, 2008 at 12:57:48AM +0300, Marius Gedminas wrote:
 - zope.server tests fail horribly with invalid file descriptor
   errors.  I cannot reproduce this error in isolation (bin/test -m
   zope.server), but I can reproduce it when I run all the tests
   together.  Some previous test is mucking stuff up.
 'bin/test -m ZEO -m zope.server' is enough to reproduce this error.
 
 Minimal test case:
 
   bin/test -pvc1 -m zope.server -t testAPPE -m ZEO -t insane
 
 The ZEO test that breaks zope.server.ftp is
 
   multiple_storages_invalidation_queue_is_not_insane (ZEO.tests.testZEO)
 
 For completeness, the full sequence of steps is
 
   check out zope.release branch 3.4
   bootstrap and run buildout
   bin/generate-buildout
   cd test
   ../bin/buildout
   bin/test -pvc1 -m zope.server -t testAPPE -m ZEO -t insane

thanks for isolating it, I've found a way to prevent the failure to occur!
The real problem comes from the ZEO tests, I've reported it here:
https://bugs.launchpad.net/zodb/+bug/257954
The final explanation is that the testrunner imports every test modules. Some 
tests modules located in zope.server and zope.app.server also import 
zope.server.dualmodechannel, which creates a pipe (a global trigger).
One of the ZEO tests close this pipe although it shouldn't. When the 
zope.server 
tests happen, the pipe is already closed and the tests fail.

Now,

We need to:
---
- release a bugfix version of zope.server 3.4.3
- release a bugfix version of zope.app.server 3.4.2
- fix z3c.formdemo and z3c.formjs against z3c.form 1.8.2 (This should be 
straightforward)

We can also:

- release a bugfix version of zope.publisher 3.4.4 that fixes an old critical 
bug ( https://bugs.launchpad.net/zope3/+bug/98440 )
- release a bugfix version of zc.zope3recipes 0.6.2, which fixes some problem 
with unwanted upgrades during tests. (although this is not needed for the 
sandboxed tests of KGS in the buildbot to pass)

We should probably:
---
- wait for setuptools 0.6c9 that fixes a major problem with subversion 1.5
- wait for the final ZODB 3.8.1.
   It would be good to include some fix for LP 257954

After that we are ready for a release of zope 3.4.
We should also probably consider waiting a bit more for the new site 
(new.zope.org) to come up, but I don't know when it will be finished. It only 
needs some content for zope2, grok, and some other pages.

Christophe


 
 Marius Gedminas
 
 
 
 
 ___
 Zope-Dev maillist  -  Zope-Dev@zope.org
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zc.zope3recipes : set offline tests everywhere

2008-08-13 Thread Christophe Combelles
Thanks for the proposals, I've added newest=false in the SetUp, as well as 
ellipsis. This seems ok for the 0.6 branch, but not enough for the trunk.

Christophe

Benji York a écrit :
 On Mon, Aug 11, 2008 at 3:27 PM, Jim Fulton [EMAIL PROTECTED] wrote:
 On Aug 11, 2008, at 5:17 AM, Chris Withers wrote:

 Christophe Combelles wrote:
 Is this change ok?
 It seems to solve the previous failures in the 3.4 kgs, and speeds
 up the test.
 I don't have a problem with the change, but this damages the
 usefulness of README.txt as documentation.

 As someone who's never used zope3recipes, I'm going to read that and
 wonder why offline = true is in there all the time as there are no
 comments or explanation.

 Myself, I'd try and find another way of getting offline=true to
 happen so that the docs can actually remain actual docs without test
 cruft strewn throughout them.

 I agree.

 A sneaky way to do this would be to change the setup code to set a
 HOME environment variable to a temporary directory
 containing .buildout/default.cfg with:
 
 I'll throw out another option: you can add doctest examples in reST
 comments to enable offline mode.  Something like this:
 
 
 .. Set offline mode so the tests run correctly (or whatever).
 
  DO THING HERE
 
 Now we foo the bar with the baz
 
  baz.foo(bar)
 
 
 When rendered to HTML (or any other target) the first part won't be
 visible, but the second part will be.
 
 If you have to do this much a global approach (like the one Jim
 suggested) would likely be better, but I wanted to demonstrate this
 approach because it can be useful when you don't want to pollute
 otherwise good documentation.

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] zc.zope3recipes : set offline tests everywhere

2008-08-09 Thread Christophe Combelles

Is this change ok?
It seems to solve the previous failures in the 3.4 kgs, and speeds up the test.


Log message for revision 89568:
  Added offline=true to every test buildout to prevent unexpected (potentially
  recursive) upgrade during tests
  


Changed:
  U   zc.zope3recipes/branches/0.6/zc/zope3recipes/README.txt
  U   zc.zope3recipes/branches/0.6/zc/zope3recipes/tests.py

-=-
Modified: zc.zope3recipes/branches/0.6/zc/zope3recipes/README.txt
===
--- zc.zope3recipes/branches/0.6/zc/zope3recipes/README.txt 2008-08-09 
10:09:05 UTC (rev 89567)
+++ zc.zope3recipes/branches/0.6/zc/zope3recipes/README.txt 2008-08-09 
10:10:49 UTC (rev 89568)
@@ -53,6 +53,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = myapp
+... offline = true
 ...
 ... [myapp]
 ... recipe = zc.zope3recipes:application
@@ -145,6 +146,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = myapp
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -288,6 +290,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = myapp
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -343,6 +346,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = myapp
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -450,6 +454,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = myapp
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -569,6 +574,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -681,6 +687,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -760,6 +767,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -850,6 +858,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -930,6 +939,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1010,6 +1020,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1112,6 +1123,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1211,6 +1223,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1307,6 +1320,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1456,6 +1470,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s
@@ -1597,6 +1612,7 @@
 ... [buildout]
 ... develop = demo1 demo2
 ... parts = instance instance2
+... offline = true
 ...
 ... [zope3]
 ... location = %(zope3)s

Modified: zc.zope3recipes/branches/0.6/zc/zope3recipes/tests.py
===
--- zc.zope3recipes/branches/0.6/zc/zope3recipes/tests.py   2008-08-09 
10:09:05 UTC (rev 89567)
+++ zc.zope3recipes/branches/0.6/zc/zope3recipes/tests.py   2008-08-09 
10:10:49 UTC (rev 89568)
@@ -32,6 +32,7 @@
 ... '''
 ... [buildout]
 ... parts = ctl
+... offline = true
 ...
 ... [ctl]
 ... recipe = zc.recipe.egg
@@ -94,6 +95,7 @@
 ... '''
 ... [buildout]
 ... parts = instance
+... offline = true
 ...
 ... [myapp]
 ... location = foo

___
Checkins mailing list
[EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/checkins




___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.app.authentication and zope.app.container broken doctests

2008-08-06 Thread Christophe Combelles

Marius Gedminas a écrit :

Something seems to be wrong with zope.app.authentication 3.4.2 and
zope.app.container 3.5.5 eggs:

Test-module import failures:

Module: zope.app.authentication.tests

ValueError: line 13 of the docstring for principalfolder.txt has 
inconsistent leading whitespace: '\r'


Module: zope.app.authentication.browser.tests

ValueError: line 18 of the docstring for principalfolder.txt has 
inconsistent leading whitespace: '\r'


Module: zope.app.container.browser.tests.test_contents_functional

ValueError: line 12 of the docstring for index.txt has inconsistent leading 
whitespace: '\r'


Module: zope.app.container.tests.test_constraints

ValueError: line 11 of the docstring for constraints.txt has inconsistent 
leading whitespace: '\r'

Ideas?  Eggs built on Windows?  Missing svn:eol-style=native properties?  Mixed
\n and \r\n line endings?

Marius Gedminas


I've re-tagged and reuploaded new versions zope.app.container 3.5.6 and 
zope.app.authentication 3.4.3. This should be ok.


Christophe







___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce

 http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Why several versions in controlled-packages.cfg?

2008-08-05 Thread Christophe Combelles
I'm wondering why there are several versions of packages in 
controlled-packages.cfg? Isn't the KGS supposed to point to a fixed set of 
unique versions ?


I'm asking because I think it's completely impossible to test every combination 
of packages:


Imagine the controlled-packages.cfg is

zope.foobar: 3.4.0
 3.4.1
zope.baz: 3.4.0
  3.4.1
  3.4.2
zope.blah: 3.5.4
   3.5.5

Suppose you want to add the bugfix release zope.foobar 3.4.2 into the KGS. When 
you launch the full test suite of the KGS, you are actually testing zope.foobar 
against all the latest versions, not ALL the versions. If zope.foobar 3.4.2 is 
not compatible with zope.baz 3.4.0, you won't see it, unless you launch the test 
for every combination of packages:

zope.foobar: 3.4.2  + zope.baz: 3.4.0 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.0 + zope.blah: 3.5.5
zope.foobar: 3.4.2  + zope.baz: 3.4.1 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.1 + zope.blah: 3.5.5
zope.foobar: 3.4.2  + zope.baz: 3.4.2 + zope.blah: 3.5.4
zope.foobar: 3.4.2  + zope.baz: 3.4.2 + zope.blah: 3.5.5

In the real world, there are a lot more packages (but ok, every package is not 
dependent of every other). So the controlled-packages is impossible to test. The 
real KGS is the set of latest versions. Why shouldn't we put only the latest 
versions in controlled-packages ?


Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] two packages badly generated

2008-08-05 Thread Christophe Combelles

Marius Gedminas a écrit :

Something seems to be wrong with zope.app.authentication 3.4.2 and
zope.app.container 3.5.5 eggs:

Test-module import failures:

Module: zope.app.authentication.tests

ValueError: line 13 of the docstring for principalfolder.txt has 
inconsistent leading whitespace: '\r'


Module: zope.app.authentication.browser.tests

ValueError: line 18 of the docstring for principalfolder.txt has 
inconsistent leading whitespace: '\r'


Module: zope.app.container.browser.tests.test_contents_functional

ValueError: line 12 of the docstring for index.txt has inconsistent leading 
whitespace: '\r'


Module: zope.app.container.tests.test_constraints

ValueError: line 11 of the docstring for constraints.txt has inconsistent 
leading whitespace: '\r'

Ideas?  Eggs built on Windows?  Missing svn:eol-style=native properties?  Mixed
\n and \r\n line endings?

Marius Gedminas


There is something seriously broken with these two packages. When I install 
zope.app.container 3.5.5 from PyPI, I'm missing some files such as add.pt, and 
all the files end with '^M'.


I've found there are two problems here :

1) All the files from the source distribution have been modified during sdist 
and include a Windows line terminator (^M). This should not happen, and makes 
the tests unhappy.


2) The distribution have been generated from a bad working environment, instead 
of a clean checkout of the tag. If I regenerate the sdist from the tag, 
everything is ok.


What should we do in such a case? Create another tag 3.5.6 == 3.5.5 and reupload 
as 3.5.6 ?


Is there any way to prevent this problem in the future?

Christophe






___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce

 http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Please no version numbers in setup.py [was: SVN: Zope2.buildout/tags/2.11.1/setup.py Pin / fix up dependencies based on comparison with monolith.]

2008-08-05 Thread Christophe Combelles

Philipp von Weitershausen a écrit :

Tres Seaver wrote:

Log message for revision 89399:
  Pin / fix up dependencies based on comparison with monolith.



Thanks for picking this up!

I do, however, strongly object to pinning versions of dependencies in 
setup.py like this. What's the point of eggifying Zope 2 in the first 
place then if not for the ability to upgrade individual libraries to 
newer versions with bugfixes or features?


Instead of pinning versions in setup.py, we should rather include a list 
of known-good versions, or even better, add the Zope 2 eggs to the Zope 
KGS. That way, by default, you'd get the known good set but you could 
deviate from it as necessary. More importantly, by having one good set 
(instead of a setup.py here, a versions.cfg there and another list 
somewhere else), the KGS becomes much easier to maintain.


The problem here (see my other message about controlled-packages.cfg) is that 
the KGS is not really tested with all the combinations : each new package is 
tested against all the latest versions, but not against *all* the versions.
That means: if you upgrade only one package for your application, something can 
break unless you upgrade all the packages to the set that has been tested when 
the package has been added to the KGS.


In my opinion we have two options:

- keep only ONE package version in the KGS (controlled-packages.cfg).
Someone wanting to upgrade a specific package for his app can do the tests 
himself, or wait for the next KGS, for example zope 3.4.1.


or

- set up a buildbot that will test every combination. A big job...

The simpler the better, I vote for 1).

Christophe



Philipp



+  install_requires=['Acquisition==2.11.1',
+'DateTime==2.11.1',
+'docutils==0.4.0',
+'ExtensionClass==2.11.1',
+'Interface==2.11.1',
+'Persistence==2.11.1',
+'pytz==2007f', # latest is fine?
+'RestrictedPython==3.4.2',
+'StructuredText==2.11.1',
+'tempstorage==2.11.1',
+'ZConfig==2.5.1',
+'zLOG==2.11.1',
+'zdaemon==2.0.1',
+'ZODB3==3.8.0',
+'zodbcode==3.4.0',
+'zope.annotation==3.4.0',
+'zope.cachedescriptors==3.4.0',
+'zope.component==3.4.0',
+'zope.configuration==3.4.0',
+'zope.contentprovider==3.4.0',
+'zope.contenttype==3.4.0',
+'zope.copypastemove==3.4.0',
+'zope.datetime==3.4.0',
+'zope.decorator==3.4.0',
+'zope.deferredimport==3.4.0',
+'zope.deprecation==3.4.0',
+'zope.documenttemplate==3.4.0',
+'zope.dottedname==3.4.0',
+'zope.dublincore==3.4.0',
+'zope.error==3.5.1',
+'zope.event==3.4.0',
+'zope.exceptions==3.4.0',
+'zope.filerepresentation==3.4.0',
+'zope.formlib==3.4.0',
+'zope.hookable==3.4.0',
+'zope.i18nmessageid==3.4.0',
+'zope.i18n==3.4.0',
+'zope.index==3.4.0',
+'zope.interface==3.4.0',
+'zope.lifecycleevent==3.4.0',
+'zope.location==3.4.0',
+'zope.minmax==3.4.0',
+'zope.modulealias==3.4.0',
+'zope.pagetemplate==3.4.0',
+'zope.proxy==3.4.0',
+'zope.publisher==3.4.0',
+'zope.rdb==3.4.0',
+'zope.schema==3.4.0',
+'zope.security==3.4.0',
+'zope.sequencesort==3.4.0',
+'zope.sendmail==3.4.0',
+'zope.server==3.4.0',
+'zope.session==3.4.0',
+'zope.size==3.4.0',
+'zope.securitypolicy==3.4.0',
+'zope.structuredtext==3.4.0',
+'zope.tales==3.4.0',
+'zope.tal==3.4.0',
+'zope.testbrowser==3.4.0',
+'zope.testing==3.4.0',
+'zope.thread==3.4.0',
+'zope.traversing==3.4.0',
+'zope.viewlet==3.4.0',
+'zope.wfmc==3.4.0',
+'zope.app.annotation==3.4.0',
+'zope.app.apidoc==3.4.3',
+

Re: [Zope-dev] Re: Zope 3.4 release policy

2008-08-04 Thread Christophe Combelles

Martijn Faassen a écrit :

Benji York wrote:
[snip]

I also have inclinations to clean up the tests that don't fail, but have
other downsides (random confusing output to stderr, not supporting
layer teardown).  I don't consider them to be release blockers, but I
think these would be nice to have in a 3.4.0 final.


3.4.0 is already at rc5, right?  If so, I'd be disinclined to do
pure refactor-y type things to it.


Agreed. I think we should just declare a 3.4.0 at this point. Perfection 
is nice but we'll never reach it anyway, and it's been a stable base for 
development for half a year now, so we have quite a bit of validation.


Let's start considering 3.4.1 and 3.5. If we get into a habit of 
releases once every few months (at least bugfix releases) there is less 
of a reason to hold off on release until things are perfect.


We should at least include all the existing bugfix releases, because there are 
some important ones. We don't need it to be called rc6, but 3.4.0 directly.


3.4.0c6 (unreleased)


- Upgraded zope.publisher to 3.4.3.
- Upgraded zope.app.authentication to 3.4.2. Removed previous versions,
  as they are not compatible with zope.app.container = 3.5.4
- Upgraded zope.app.container to 3.5.5
- Upgraded zope.testing 3.5.1 to 3.5.4.
- Upgraded zc.buildout 1.0.0 to 1.1.1.

What are we doing for the changelog of zope.release? Should we finally merge 
KGS-HISTORY.txt into CHANGES.txt or leave both files as is ?


Christophe




Regards,

Martijn

___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )




___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] bad zope.size to remove from PyPI

2008-08-04 Thread Christophe Combelles

I've found another one, detected by zope.release's list-latest:
http://pypi.python.org/pypi/zope.app.externaleditor/3.4.0-r81494
But it seems hidden in pypi.


Christophe Combelles a écrit :

Hi,

could someone remove this package from the PyPI :
http://pypi.python.org/pypi/zope.size/3.4dev-r73090

This is an empty development version, considered more recent by PyPI 
than the latest released version 3.4.0. (which is r78211)


Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )




___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Re: [Checkins] SVN: zope.release/branches/3.4/ * Added latest version of zope.app.security to avoid deprecation

2008-08-01 Thread Christophe Combelles

Stephan Richter a écrit :

Log message for revision 89104:
  * Added latest version of zope.app.security to avoid deprecation 
warnings.
  
  * Added history file for the KGS to hopefully create better release 
notes.


Did you miss the CHANGES.txt in zope.release ? We have two histories now.

How did you choose the 3.4.0c5 version? I mean, where does the 5 come from?

Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Re: [Checkins] SVN: zope.release/branches/3.4/ * Added latest version of zope.app.security to avoid deprecation

2008-08-01 Thread Christophe Combelles

Stephan Richter a écrit :

On Friday 01 August 2008, Christophe Combelles wrote:

Did you miss the CHANGES.txt in zope.release ? We have two histories now.


Nope, but that file tracks the package -- source code -- changes of 
zope.release.


I wanted a separate file that tracks the changes to the 
controlled-packages.cfg file.


In my understanding, there is almost no source code in 'zope.release', since it 
has been moved into 'zope.kgs'. So there should be very few entries in 
CHANGES.txt, and I'm not sure there is a real interest in having two separate 
files. In my opinion, it adds confusion, people are more used to maintain 
CHANGES.txt.
The other problem is there is no tag for c1, c2, c3 and c4. I thought 
zope.release was meant to represent the release number of zope.


I would tend to:
- create a tag for all missing candidates
- merge KGS-HISTORY.txt into CHANGES.txt and recover missing information from 
published control-packages.cfg


Christophe




How did you choose the 3.4.0c5 version? I mean, where does the 5 come
from?


We have been doing c* KGS releases all along. See 


http://download.zope.org/zope3.4/intro.html

I just have not bothered updating the Zope3 tree, making packages and 
announcements. It just costs too much time. Unless Marius or someone else 
signs up for producing TAR ball releases and announces them, I will only 
create a TAR ball and announcement for Zope 3.4.0 final.


Regards,
Stephan


___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Re: [Checkins] SVN: zope.release/branches/3.4/ * Added latest version of zope.app.security to avoid deprecation

2008-08-01 Thread Christophe Combelles

Stephan Richter a écrit :

On Friday 01 August 2008, Christophe Combelles wrote:

I wanted a separate file that tracks the changes to the
controlled-packages.cfg file.

In my understanding, there is almost no source code in 'zope.release',
since it has been moved into 'zope.kgs'. So there should be very few
entries in CHANGES.txt, and I'm not sure there is a real interest in having
two separate files. In my opinion, it adds confusion, people are more used
to maintain CHANGES.txt.


Okay, I am open to suggestions and want to hear others give an opinion too.


The other problem is there is no tag for c1, c2, c3 and c4. I thought
zope.release was meant to represent the release number of zope.


It is. I and Marius simply did not create those tags.


I would tend to:
- create a tag for all missing candidates


Cool, I take you up on that.


Done.




- merge KGS-HISTORY.txt into CHANGES.txt and recover missing information
from published control-packages.cfg


These are two tasks:

- Update KGS-HISTORY.txt to contain the changes of the previous releases. 
(Luckily you can just look at the SVN changelog for controlled-packages.cfg.) 
I take you up on that one as well! :-)


I've updated KGS-HISTORY.txt and CHANGES.txt.

Actually KGS-HISTORY.txt is just a reformatted svn diff between successive 
versions. I'm not sure it has a real added value, excepted when there are 
explanations about the version upgrades.


Christophe



- Merge KGS-HISTORY.txt into CHANGES.txt. I want to hear a couple more 
opinions on that.


Regards,
Stephan


___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] bad zope.size to remove from PyPI

2008-08-01 Thread Christophe Combelles

Hi,

could someone remove this package from the PyPI :
http://pypi.python.org/pypi/zope.size/3.4dev-r73090

This is an empty development version, considered more recent by PyPI than the 
latest released version 3.4.0. (which is r78211)


Christophe
___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.app.container 3.5.4 bugfix release

2008-07-17 Thread Christophe Combelles

Baiju M a écrit :

- Christophe Combelles [EMAIL PROTECTED] wrote:

I've added a tag for the 3.5.4 bugfix release of zope.app.container.

Could someone please add me on the owners list on pypi so that I can
upload it?


Your PyPI ID ?


ccomb



--
Baiju M





___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] zope.app.container 3.5.4 released

2008-07-17 Thread Christophe Combelles

Baiju M a écrit :

- Christophe Combelles [EMAIL PROTECTED] wrote:

Baiju M a écrit :

- Christophe Combelles [EMAIL PROTECTED] wrote:

I've added a tag for the 3.5.4 bugfix release of

zope.app.container.

Could someone please add me on the owners list on pypi so that I

can

upload it?

Your PyPI ID ?

ccomb


Done.


Released!




--
Baiju M





___
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope )


  1   2   >