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

2013-04-26 Thread Gediminas Paulauskas
2013/4/26 Zope tests summarizer nore...@zope.org:
 This is the summary for test reports received on the
 zope-tests list between 2013-04-24 00:00:00 UTC and 2013-04-25 00:00:00 UTC:

 [1]FAILED  Still Failing - zopetoolkit_trunk - Build # 244
https://mail.zope.org/pipermail/zope-tests/2013-April/074107.html


 [2]FAILED  Still Failing - zopetoolkit_trunk - Build # 248
https://mail.zope.org/pipermail/zope-tests/2013-April/074109.html

The same BTrees setup_requires persistent error.

 [3]FAILED  winbot / z3c.baseregistry_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074125.html

github offline.

 [4]FAILED  winbot / z3c.contents_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074108.html

Last build successful.

 [5]FAILED  winbot / zc.resourcelibrary_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074122.html


 [6]FAILED  winbot / zope.app.generations_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074123.html


 [7]FAILED  winbot / zope.container_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074124.html


 [8]FAILED  winbot / zope.traversing_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074126.html

github offline.

-- 
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-tests - FAILED: 4, OK: 12

2013-04-25 Thread Gediminas Paulauskas
2013/4/25 Marius Gedminas mar...@gedmin.as:
 On Thu, Apr 25, 2013 at 09:49:28AM -0400, Tres Seaver wrote:
 On 04/25/2013 04:36 AM, Marius Gedminas wrote:
  So latest stable ZODB3 (3.10.5) is incompatible with the two latest
  stable persistent releases (4.0.5 and 4.0.6).
 
  What should we do?  Release ZODB3 3.10.6 with a backport of these
  patches?

 ZODB 3.10 bundles its own version of persistent:  the standalone one
 shouldn't be used at all if ZODB 3.10 is in play.

 Yet somehow we're getting both in a z3c.contents buildout.  Note that
 z3c.contents doesn't directly require either one.

 It looks like we're getting persistent via BTrees 4.0.5, and we're
 getting BTrees via zope.annotation 4.2.0, and we're getting
 zope.annotation via zope.copypastemove 3.8.0, which is a direct
 requirement of z3c.contents.

 Are BTrees bundled with ZODB3 as well?  (Yes.)

 Can setuptools dependencies express complicated Debian-package-like
 concepts like ZODB3 provides BTrees, persistent and ZODB3 conflicts
 with BTrees, persistent?

 Are there other ways of avoiding a flag day?  I don't think we can
 reasonably require that no final-version PyPI package may depend on
 BTrees or persistent until ZODB 4.0.0 final is finally out.

I have removed some deprecated ftest dependencies like
zope.app.securitypolicy that pulls in the whole Zope 3. Tests passed.

Then I pinned some versions until nothing required ZODB3 any more.

Let's see how winbot likes it.

--
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-tests - FAILED: 4, OK: 12

2013-04-24 Thread Gediminas Paulauskas
2013/4/24 Zope tests summarizer nore...@zope.org:
 This is the summary for test reports received on the
 zope-tests list between 2013-04-22 00:00:00 UTC and 2013-04-23 00:00:00 UTC:

 [4]FAILED  winbot / z3c.form_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-April/074075.html

The tests were using an xpath query like './/xmlns:ul[1]' but
expecting multiple ul tags. Those tests should have failed long ago,
and they do fail on my machine in much older versions of z3c.form. The
difference is a newer version of libxml2 = 2.9.0 (the version in
Ubuntu 13.04).

I have fixed the test and pushed to z3c.form master.
___
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: 2, OK: 20, UNKNOWN: 1

2012-12-09 Thread Gediminas Paulauskas
2012/12/7 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 12/07/2012 01:11 PM, Gediminas Paulauskas wrote:
 2012/12/7 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

 On 12/07/2012 01:52 AM, Marius Gedminas wrote:
 [3]FAILED  winbot / zope.app.i18n_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2012-December/069796.html




 Error in test testNoTargetLanguage
 (zope.app.i18n.tests.test_translationdomain.TestTranslationDomain)
 Traceback (most recent call last): File
 c:\Python26_32\lib\unittest.py, line 279, in run testMethod()
 File
 c:\eggs\zope.i18n-3.8.0-py2.6.egg\zope\i18n\tests\test_itranslationdomain.py,


 line 99, in testNoTargetLanguage eq(translate('short_greeting',
 context=context, default=42), 42) File
 c:\buildslave\zope.app.i18n\build\src\zope\app\i18n\translationdomain.py,


 line 74, in translate catalog_names =
 self._catalogs.get(target_language, []) TypeError: Object has
 default comparison

 Here, the 'target_langeage' returned by the negotiator is None,
 which the OOBTree is refusing to treat as a key (because its
 comparison semantics are undefined across process boundaries /
 Python versions)::

 from BTrees.OOBTree import OOBTree x = OOBTree() x[None] = 1
 Traceback (most recent call last): File stdin, line 1, in
 module TypeError: Object has default comparison

 Such keys haven't been allowed since::

 r117933 | jim | 2010-10-26 17:14:00 -0400 (Tue, 26 Oct 2010) | 7
 lines

 Bug Fixed - BTrees allowed object keys with insane comparison.
 (Comparison inherited from object, which compares based on
 in-process address.) Now BTrees raise TypeError is an attempt is
 made to save a key with comparison inherited from object. (This
 doesn't apply to old-style class instances.)

 The error happens in get, not set, should it?

 The C code throws the error whenever dealing with a user-supplied key
 which cannot be safely compared to existing keys.

 Otherwise, a patch for zope.app.i18n to fix this case is attached
 (not committed).

 +1 for your patch.

ok, committed.

-- 
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-tests - FAILED: 2, OK: 20, UNKNOWN: 1

2012-12-07 Thread Gediminas Paulauskas
2012/12/7 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 12/07/2012 01:52 AM, Marius Gedminas wrote:
 [3]FAILED  winbot / zope.app.i18n_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2012-December/069796.html


 Error in test testNoTargetLanguage
 (zope.app.i18n.tests.test_translationdomain.TestTranslationDomain)
 Traceback (most recent call last): File
 c:\Python26_32\lib\unittest.py, line 279, in run testMethod() File
 c:\eggs\zope.i18n-3.8.0-py2.6.egg\zope\i18n\tests\test_itranslationdomain.py,
 line 99, in testNoTargetLanguage eq(translate('short_greeting',
 context=context, default=42), 42) File
 c:\buildslave\zope.app.i18n\build\src\zope\app\i18n\translationdomain.py,
 line 74, in translate catalog_names =
 self._catalogs.get(target_language, []) TypeError: Object has default
 comparison

 Here, the 'target_langeage' returned by the negotiator is None, which the
 OOBTree is refusing to treat as a key (because its comparison semantics
 are undefined across process boundaries / Python versions)::

   from BTrees.OOBTree import OOBTree
   x = OOBTree()
   x[None] = 1
  Traceback (most recent call last):
File stdin, line 1, in module
  TypeError: Object has default comparison

 Such keys haven't been allowed since::

  r117933 | jim | 2010-10-26 17:14:00 -0400 (Tue, 26 Oct 2010) | 7 lines

  Bug Fixed
  - BTrees allowed object keys with insane comparison. (Comparison
inherited from object, which compares based on in-process address.)
Now BTrees raise TypeError is an attempt is made to save a key with
comparison inherited from object. (This doesn't apply to old-style
class instances.)

The error happens in get, not set, should it?

Otherwise, a patch for zope.app.i18n to fix this case is attached (not
committed).

-- 
Gediminas


zopeappi18n-with-zodb4.diff
Description: Binary data
___
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: 1, OK: 40

2012-05-26 Thread Gediminas Paulauskas
2012/5/26 Marius Gedminas mar...@gedmin.as:
 On Fri, May 25, 2012 at 10:58:20PM -0400, Tres Seaver wrote:
 On 05/25/2012 09:00 PM, Zope tests summarizer wrote:
  [1]    FAILED  Zope 3.4 KGS / Python2.4.6 64bit linux
  https://mail.zope.org/pipermail/zope-tests/2012-May/063520.html

 Ugh, the old eccentric FTP HELP failure

 
 
  Failure in test testHELP (zope.server.ftp.tests.test_ftpserver.Tests)
  Traceback (most recent call last): File
  /usr/local/python2.4.6/lib/python2.4/unittest.py, line 260, in run
  testMethod() File
  /home/ccomb/buildout-eggs/zope.server-3.4.3-py2.4.egg/zope/server/ftp/tests/test_ftpserver.py,
  line 280, in testHELP self.assertEqual(self.execute('HELP', 1),
  result) File /usr/local/python2.4.6/lib/python2.4/unittest.py, line
  333, in failUnlessEqual raise self.failureException, \ 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'


 I have no idea why this would be failing *now*, as opposed to yesterday.

 It's nondeterministic.

 I once posted a proposed patch:
 https://mail.zope.org/pipermail/zope-dev/2010-December/042138.html

 I didn't commit it since I was completely unable to reproduce the
 failure on my machine, and so couldn't verify that it was the correct
 fix.

I have committed this fix a year ago:

http://zope3.pov.lt/trac/changeset/121089/zope.server/trunk

and also merged to 3.6 branch. But there is no branch for Zope 3.4.


-- 
Gediminas Paulauskas
___
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.interface 4.0.0 considered annoying.

2012-05-21 Thread Gediminas Paulauskas
2012/5/20 Tres Seaver tsea...@palladion.com:
 On 05/19/2012 07:23 PM, Jim Fulton wrote:
 On Sat, May 19, 2012 at 5:59 PM, Tres Seaver tsea...@palladion.com
 wrote:
 On 05/19/2012 12:12 PM, Jim Fulton wrote:
 The declaration-syntax warnings in the zope.interface 4.0.0 are
 annoying and mostly pointless.

 There will be enough pain in porting applications to Python 3,
 avoiding the surprise of having to use a different
 interface-declaration syntax will not be of any consequence.

 While the deprecation warning may provide some tiny benefit, the
 annoyance, especially for applications or libraries that still
 support Python 2.5 far outweights the benefit.

 We're in an odd spot:  the Python3 support for zope.interface
 mostly works, but the class advice bits (implements,
 implementsOnly, classProvides) fail silently under Python3 before
 4.0.0:  they literally have no effect due to changes in class
 initialization machinery. zope.interface 4.0.0 changes those silent
 failures into exceptions (which is what I thought you were going to
 complain about).

 I'd forgotten the fail silently bit.  Can't we make the fail loudly
 for Python 3?

 They already do:  4.0.0 makes them exceptions under Python3:  that fact
 was actually my rationale for the warnings under Python2, to allow folks
 to find and remediate them before porting.

If they are exceptions under Python 3, developers will get them and
have to fix when porting to Python 3. There is a lot of other work to
be done at the same time. But under Python 2, implements and friends
continue to work, so the warnings are very annoying.

 I will release a 4.0.1 silencing the warnings unless somebody speaks up
 in their favor.

Please, only warn on Python 3.

-- 
Gediminas Paulauskas
___
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] SVN: zope.deprecation/trunk/ Revert a move of `README.txt` to unbreak ``zope.app.apidoc``.

2012-04-17 Thread Gediminas Paulauskas
2012/4/17 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 03/15/2012 05:21 AM, Marius Gedminas wrote:

I have made this change, not Marius.

 Log message for revision 124600: Revert a move of `README.txt` to
 unbreak ``zope.app.apidoc``.


 Changed: _U  zope.deprecation/trunk/ U
 zope.deprecation/trunk/CHANGES.txt U zope.deprecation/trunk/README.txt
 U   zope.deprecation/trunk/setup.py A
 zope.deprecation/trunk/src/zope/deprecation/README.txt


 I'd like to argue against this reversion:  the ZTK 1.0 / 1.1 checkouts
 should all be using the stable 3.4 branch.  If the z.a.apidoc trunk needs
 fixing (why in hell does it depend on the existince of a README.txt at
 package scope in another package?) let's fix it there.

What if I use ZTK 1.1 but still want zope.app.apidoc (that was removed
from the set)?

The README.txt in project root is not included in the egg. So I would
have to remove 'Zope Deprecation' chapter from the apidoc Book and
make a new major release of this deprecated module.

Instead, I restored the location of README.txt, a move that does not
have any benefit, so that an app that includes zope.app.apidoc would
start, and I do not need to remove any content. Chose lesser evil to
fix breakage.

-- 
Gediminas Paulauskas
___
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: 12, OK: 32

2012-03-12 Thread Gediminas Paulauskas
2012/3/12 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 03/11/2012 09:00 PM, Zope tests summarizer wrote:

 [6]    FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2012-March/059167.html


 [7]    FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2012-March/059169.html


 [8]    FAILED  ZTK 1.0dev / Python2.6.7 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2012-March/059168.html


 The buildout step for these three seems to be related to a
 partially-unpinned ZODB dependency::


 The version, 3.9.7, is not consistent with the requirement,
 'ZODB3=3.10'. While: Installing test-zopeapp. Error: Bad version
 3.9.7 program finished with exit code 0 elapsedTime=1561.566938


 AFAIK, ZTK 1.0 is pinned to 'ZODB=3.9.7';  I don't know what is causing
 something to require 'ZODB=3.10'.  Maybe a newly-released package has
 snuck into the mix?

It is zope.app.publication 3.14.0, see http://zope3.pov.lt/trac/changeset/124535

-- 
Gediminas Paulauskas
___
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: 2, OK: 42

2012-02-21 Thread Gediminas Paulauskas
2012/2/21 Zope tests summarizer nore...@zope.org:
 Non-OK results
 --

 [1]    FAILED  winbot / zope.app.locales_py_265_32
       https://mail.zope.org/pipermail/zope-tests/2012-February/058374.html


 [2]    FAILED  winbot / zope.app.server_py_265_32
       https://mail.zope.org/pipermail/zope-tests/2012-February/058372.html

Both builders have newer, green builds.

-- 
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-tests - FAILED: 26, OK: 39, UNKNOWN: 2

2012-02-08 Thread Gediminas Paulauskas
2012/2/8 Zope tests summarizer nore...@zope.org:
 This is the summary for test reports received on the
 zope-tests list between 2012-02-06 00:00:00 UTC and 2012-02-07 00:00:00 UTC:

 See the footnotes for test reports of unsuccessful builds.

 An up-to date view of the builders is also available in our
 buildbot documentation:
 http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

 Reports received
 

       Bluebream / Python2.5.5 64bit linux
       Bluebream / Python2.6.7 64bit linux
       Bluebream / Python2.7.2 64bit linux
 [1]    UNKNOWN : Zope-trunk Python-2.6.6 : Linux
 [2]    UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux
       ZTK 1.0 / Python2.4.6 Linux 64bit
       ZTK 1.0 / Python2.5.5 Linux 64bit
       ZTK 1.0 / Python2.6.7 Linux 64bit
       ZTK 1.0dev / Python2.4.6 Linux 64bit
       ZTK 1.0dev / Python2.5.5 Linux 64bit
       ZTK 1.0dev / Python2.6.7 Linux 64bit
 [3]    ZTK 1.1 / Python2.5.5 Linux 64bit
 [4]    ZTK 1.1 / Python2.6.7 Linux 64bit
 [5]    ZTK 1.1 / Python2.7.2 Linux 64bit
       Zope 3.4 KGS / Python2.4.6 64bit linux
       Zope 3.4 KGS / Python2.5.5 64bit linux
       Zope 3.4 Known Good Set / py2.4-32bit-linux
       Zope 3.4 Known Good Set / py2.4-64bit-linux
       Zope 3.4 Known Good Set / py2.5-32bit-linux
       Zope 3.4 Known Good Set / py2.5-64bit-linux
       Zope Buildbot / zope2.12-py2.6 slave-ubuntu32
       Zope Buildbot / zope2.12-py2.6 slave-ubuntu64
       Zope Buildbot / zope2.13-py2.6 slave-ubuntu32
       Zope Buildbot / zope2.13-py2.6 slave-ubuntu64
       Zope Buildbot / zope2.13-py2.7 slave-ubuntu32
       Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
 [6]    Zope Buildbot / zope2.14-py2.6 slave-ubuntu32
 [7]    Zope Buildbot / zope2.14-py2.6 slave-ubuntu64
 [8]    Zope Buildbot / zope2.14-py2.7 slave-ubuntu32
 [9]    Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
       Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32
       Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64
       Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32
       Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64
       Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32
       Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64
 [10]   Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32
 [11]   Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64
 [12]   Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32
 [13]   Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64
 [14]   Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32
 [15]   Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64
 [16]   Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32
 [17]   Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64
       Zope-2.10 Python-2.4.6 : Linux
       Zope-2.11 Python-2.4.6 : Linux
       Zope-2.12 Python-2.6.6 : Linux
       Zope-2.12-alltests Python-2.6.6 : Linux
       Zope-2.13 Python-2.6.6 : Linux
       Zope-2.13-alltests Python-2.6.6 : Linux
       winbot / ZODB_dev py_265_win32
       winbot / ZODB_dev py_265_win64
       winbot / ZODB_dev py_270_win32
       winbot / ZODB_dev py_270_win64
 [18]   winbot / zope.testrunner_py_265_32
       winbot / ztk_10 py_254_win32
       winbot / ztk_10 py_265_win32
 [19]   winbot / ztk_10 py_265_win64
 [20]   winbot / ztk_11 py_254_win32
 [21]   winbot / ztk_11 py_265_win32
 [22]   winbot / ztk_11 py_265_win64
 [23]   winbot / ztk_11 py_270_win32
 [24]   winbot / ztk_11 py_270_win64
 [25]   winbot / ztk_dev py_265_win32
 [26]   winbot / ztk_dev py_265_win64
 [27]   winbot / ztk_dev py_270_win32
 [28]   winbot / ztk_dev py_270_win64

The majority of failures are in zope.testrunner, due to recent update
of versions. The offending one is testtools 0.9.13. With testtools
0.9.12 the tests pass.

-- 
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-tests - FAILED: 28, OK: 43

2012-01-23 Thread Gediminas Paulauskas
2012/1/23 Marius Gedminas mar...@gedmin.as:
 On Mon, Jan 23, 2012 at 01:00:02AM +, Zope tests summarizer wrote:
 Non-OK results
 --

 [6]    FAILED  ZTK 1.0 / Python2.4.6 Linux 64bit
        https://mail.zope.org/pipermail/zope-tests/2012-January/056532.html

 Failure in test test_ErrorLog_unicode 
 (zope.error.tests.ErrorReportingUtilityTests)
 AssertionError: 'Traceback (most recent call last):\n  Module 
 zope.error.tests, line 36, in getAnErrorInfo\n    raise Error(value)\nError: 
 unprintable instance object\n'
            != u'Traceback (most recent call last):\n  Module 
 zope.error.tests, line 36, in getAnErrorInfo\n    raise Error(value)\nError: 
 lt;unprintable instance objectgt;\n'

 so some unexpected HTML-quoting appears.

 Reason: http://zope3.pov.lt/trac/changeset/124062

 I assume the code is now correct and it is the test that needs to be
 fixed.

Note that this zope.error test fails only on python 2.4 and 2.5, so
there are some quoting differences between them.

 [7]    FAILED  ZTK 1.0 / Python2.5.5 Linux 64bit
        https://mail.zope.org/pipermail/zope-tests/2012-January/056534.html

 Same error.

 [8]    FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit
        https://mail.zope.org/pipermail/zope-tests/2012-January/056546.html

 Same zope.error error, and then

 ZopeXMLConfigurationError: File 
 /home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/src/zope.app.generations/src/zope/app/generations/ftesting.zcml,
  line 13.2-13.47
    ConfigurationError: ('Invalid value for', 'package', 'ImportError: Module 
 zope.app has no global authentication')

 [9]    FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit
        https://mail.zope.org/pipermail/zope-tests/2012-January/056548.html

 Same two errors.

 [10]   FAILED  ZTK 1.0dev / Python2.6.7 Linux 64bit
        https://mail.zope.org/pipermail/zope-tests/2012-January/056547.html

 Same zope.app.generations failure.

This was caused by my checkin
http://zope3.pov.lt/trac/changeset/124100/zope.app.zcmlfiles

Remove include of zope.app.zopeappgenerations that is not useful unless
upgrading a database older than Zope 3.4. This cuts the last dependency on
zope.app.authentication from the ZTK.

I have now merged a fix to zope.app.generations/branches/3.6 that is
used by ZTK 1.0dev

-- 
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-tests - FAILED: 5, OK: 42

2011-11-30 Thread Gediminas Paulauskas
2011/11/30 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 [1]    FAILED  winbot / zope.keyreference_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2011-November/053374.html


 [2]    FAILED  winbot / ztk_dev py_265_win32
 https://mail.zope.org/pipermail/zope-tests/2011-November/053375.html


 [3]    FAILED  winbot / ztk_dev py_265_win64
 https://mail.zope.org/pipermail/zope-tests/2011-November/053376.html


 [4]    FAILED  winbot / ztk_dev py_270_win32
 https://mail.zope.org/pipermail/zope-tests/2011-November/053377.html


 [5]    FAILED  winbot / ztk_dev py_270_win64
 https://mail.zope.org/pipermail/zope-tests/2011-November/053378.html


 All five failures are due to the removal of 'zope.testing' from the
 'tests_require' of zope.keyreference, and look like::

Oops. I broke a module not touched for years the last minute before release.

I fixed this failure by avoiding zope.testing, not re-adding it.
Released as zope.keyreference 3.6.4

Strangely, tests passed for me in zope.keyreference/bin/test, that's
why I was not aware of the problem.

But now I tested as buildbot does from
zopetoolkit/bin/test-ztk-zope.keyreference could reproduce and fix it.

-- 
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] SVN: zope.catalog/trunk/ Fix ZPL version in file headers

2011-11-29 Thread Gediminas Paulauskas
2011/11/29 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/29/2011 11:47 AM, Gediminas Paulauskas wrote:
 2011/11/29 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

 On 11/29/2011 10:39 AM, Gediminas Paulauskas wrote:

 ===


 - --- zope.catalog/trunk/setup.py       2011-11-27 22:25:03 UTC (rev 123517)
 +++ zope.catalog/trunk/setup.py       2011-11-29 15:39:53 UTC (rev
 123518) @@ -26,7 +26,7 @@

 setup(name = 'zope.catalog', version = '3.8.2dev', -
 author='Zope Foundation and Contributors', +      author='Zope
 Corporation and Contributors',
 author_email='zope-dev-cwuwpebw...@public.gmane.org',
 description='Cataloging and Indexing Framework for the Zope
 Toolkit', long_description=(


 Hmm, that doesn't look right:  ZC transferred all ownership of code
 to the foundation.

 I've got mails from people in Zope Corporation where they complained
 that author is changed without reason. Copyright is transferred to
 Foundation, but author is still the Corporation. Since there was no
 release with changed author, I reverted this change.

 Zope Corp. didn't write the code for either zope.catalog or
 zope.app.catalog (from which it was drawn):  all that code is written by
 individuals, many of whom were not employees of ZC at the time.  If there
 *is* a single (primary) author, then listing that *person* as author is
 fine, but otherwise the Foundation works better than ZC as a collective
 author.

OK I will stop looking at who the author is :)

I just released a few modules, because I needed a tarball with all the
LICENSE.txt files.

I wanted only to avoid a change in the author field compared to the
previous release.




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

 iEYEARECAAYFAk7VFC4ACgkQ+gerLs4ltQ6jOwCfaXPIkmDhLA1LRRk6/QQ651zl
 5oIAoMiPk7suvs9iM1K8Lk9zePOuHITU
 =4Osf
 -END PGP SIGNATURE-




-- 
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-tests - FAILED: 4, OK: 40, UNKNOWN: 2

2011-11-20 Thread Gediminas Paulauskas
2011/11/20 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/19/2011 03:18 PM, Wolfgang Schnerring wrote:
 * Tres Seaver tsea...@palladion.com [2011-11-19 14:31]:
 [1]    UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052856.html



 [2]    UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052857.html



 These two are also tied to the missing zope.publisher 3.13.0 release.

 Mea culpa about the missing release; I don't actually know what
 happened, since I use zest.releaser, so there isn't all that much
 that should go wrong, usually. And I certainly didn't notice anything
 was amiss. Sorry about that. I've uploaded the release just now.

 [3]    FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-November/052845.html



 We need to tie ZTK 1.0dev to a backward-compatible branch of
 zope.publisher (no longer the trunk).

 Ah. Right, that makes sense. 3.12.x then?

 Yep:  I would make the 3.12 branch from the trunk as of r121101 (tiny fix
 after 3.12.6).  Then we update the ZTK 1.0 and 1.1 dev setup to use that
 branch.

I have made a 3.12 branch (from r123091) and updated ZTK 1.0 to use it.

ZTK 1.1 is fine.

-- 
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.deprecation

2011-09-05 Thread Gediminas Paulauskas
2011/9/5 Chris McDonough chr...@plope.com:
 On Mon, 2011-09-05 at 09:53 +0200, Hanno Schlichting wrote:
 On Mon, Sep 5, 2011 at 1:09 AM, Chris McDonough chr...@plope.com wrote:
  I've given Python 3 support to zope.deprecation at
  http://svn.zope.org/zope.deprecation/branches/chrism-unittesting/
 
  - Which Python versions is this thing meant to support?  I have it
   functioning under 2.5, 2.6, 2.7 (and 3.2).  Do we need it
   to support 2.4?

 We no longer need Python 2.4 compatibility for new stuff (only for
 bugfixes to ZTK 1.0).

  - I presume the version number after merge should be bumped to
   3.5 (it was branched from 3.42dev)?

 Yes, we treat Python 3 compatibility as a new feature. So this will
 only go into ZTK trunk.

 Great.  I've merged my branch into the trunk as per the above.
 Apparently I don't have owner access on the thing on PyPI so I can't
 make a release.  Currently owners of the zope.deprecation package are:
 J1m, fdrake, menesis.  It'd be nice to either get owner/maintainer
 access or for someone to create a 3.5 release.

I have added chrism to owners.
Leaving to you to make the release.
Glanced at the changes, looks good to me.

-- 
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.interface versions, ZTK 1.0 and later

2011-08-17 Thread Gediminas Paulauskas
2011/8/13 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 08/12/2011 02:46 PM, Tres Seaver wrote:

  %
  Proposal 

 - Revert ZTK 1.0 to use zope.interface 3.6.1.  (We can skip this part
 if the next step goes quickly).

 - Create a 3.6 branch in SVN, and revert all the post-3.6.1 changes
 on it.  Release a new 3.6.6 from this branch, possibly after applying
 a new, more minimal fix for LP #570942.

 - Bump ZTK 1.0 to use the zope.interface 3.6.6.

 - Freeze development on the 3.6 branch.

 - Release a 3.7.0 version from the trunk, with all the porting
 changes intact.  Update ZTK 1.1 to use 3.7.0,
  %
 

 Done.

It's all good, except that the tests of alternative solution in 3.6.6
do not pass [1].

Also I thought 3.6.2 was good for ZTK 1.0, as it worked on python 2.4 - 3.2.
Only the sorting improvement in next versions broke something.

[1] 
http://buildbot.afpy.org/ztk1.0/builders/Python2.6.5%20Linux%2064bit/builds/344/steps/test%20ztk/logs/stdio

-- 
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] SVN: zope.interface/trunk/ Fix a regression introduced in 3.6.4, that made one zope.app.interface test fail

2011-08-17 Thread Gediminas Paulauskas
2011/8/6 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 08/04/2011 10:18 AM, Gediminas Paulauskas wrote:
 Log message for revision 122462: Fix a regression introduced in
 3.6.4, that made one zope.app.interface test fail


 Changed: U   zope.interface/trunk/CHANGES.txt U
 zope.interface/trunk/src/zope/interface/interface.py

 -=- Modified: zope.interface/trunk/CHANGES.txt
 ===
 --- zope.interface/trunk/CHANGES.txt  2011-08-04 13:44:20 UTC (rev
 122461) +++ zope.interface/trunk/CHANGES.txt  2011-08-04 14:18:37 UTC
 (rev 122462) @@ -11,10 +11,12 @@

 - Fix testing deprecation warnings issued when tested under Py3K.

 +- Fix ``InterfaceClass.__hash__`` to match comparison function. +
 3.6.4 (2011-07-04) --

 -- LP 804951:  InterfaceClass instances were unhashable under Python
 3.x. +- LP #804951:  InterfaceClass instances were unhashable under
 Python 3.x.

 3.6.3 (2011-05-26) --

 Modified: zope.interface/trunk/src/zope/interface/interface.py
 ===
 --- zope.interface/trunk/src/zope/interface/interface.py      2011-08-04
 13:44:20 UTC (rev 122461) +++
 zope.interface/trunk/src/zope/interface/interface.py  2011-08-04
 14:18:37 UTC (rev 122462) @@ -682,7 +682,8 @@ return (n1  n2) - (n1
  n2)

 def __hash__(self): -        return hash((self.__name__,
 self.__module__)) +        return hash((getattr(self, '__name__',
 ''), +                     getattr(self, '__module__', '')))

 I don't think this is a regression -- how do you legitimately create an
 interface without both those attributes?   The point of the comparison
 function is to work even when handed a non-Interface object as one of
 the two terms being compared, which doesn't apply to the case of a hash.
 If there is code in zope.app.interface which is constructing a class
 derived from Interface but which doesn't call Interface.__init__ before
 hashing the instance, that code is *broken*, and should be fixed.

It was my attempt to fix tests that were failing for more than a week,
and it worked. zope.app.interface might be broken, but I couldn't
understand why
it failed, especially the foreign connection exception. Here I saw
asymmetry between __eq__ and __hash__, and I still feel that my fix
was better than returning 1.

In addition to zope.app.interface, there was another problem with
Tahoe-LAFS: https://bugs.launchpad.net/zope.interface/+bug/811792 that
Tres helped to solve.

-- 
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] [Checkins] SVN: zope.interface/trunk/ Correct comparison of interfaces from different modules but with the same name.

2011-06-14 Thread Gediminas Paulauskas
Hello,

I ran tests in some zope modules with python3.2, and got an exception:

$ cd zope.proxy
$ python3.2 setup.py test
...
  File 
/home/menesis/src/zope.proxy/build/lib.linux-i686-3.2/zope/proxy/__init__.py, 
line 16, in module
from zope.interface import moduleProvides
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/__init__.py,
 line 53, in module
from zope.interface.interface import Interface, _wire
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/interface.py,
 line 710, in module
Interface = InterfaceClass(Interface, __module__ = 'zope.interface')
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/interface.py,
 line 479, in __init__
Specification.__init__(self, bases)
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/interface.py,
 line 266, in __init__
self.__bases__ = tuple(bases)
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/interface.py,
 line 290, in __setBases
self.changed(self)
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/interface.py,
 line 309, in changed
ancestors = ro(self)
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/ro.py,
 line 22, in ro
return mergeOrderings([_flatten(object)])
  File 
/home/menesis/src/zope.proxy/zope.interface-3.6.3-py3.2-linux-i686.egg/zope/interface/ro.py,
 line 51, in mergeOrderings
if o not in seen:
TypeError: unhashable type: 'InterfaceClass'

I found the following to explain what happens:
http://stackoverflow.com/questions/1608842/types-that-define-eq-are-unhashable-in-python-3-x

And a commit which does exactly that: define an __eq__ but not __hash__.

Adding a simple

def __hash__(self):
return id(self)

fixes the problem.

This change was released as zope.interface 3.6.3. Earlier version does not have 
this problem.

On Thu, 2011-05-26 12:10-0400, Tres Seaver wrote:
 Log message for revision 121819:
   Correct comparison of interfaces from different modules but with the same 
 name.
   
   Fixes LP #570942.
   
 
 Changed:
   U   zope.interface/trunk/CHANGES.txt
   U   zope.interface/trunk/src/zope/interface/interface.py
   U   zope.interface/trunk/src/zope/interface/tests/test_interface.py
   U   zope.interface/trunk/src/zope/interface/tests/test_sorting.py
 
 -=-
 Modified: zope.interface/trunk/CHANGES.txt
 ===
 --- zope.interface/trunk/CHANGES.txt  2011-05-26 11:27:21 UTC (rev 121818)
 +++ zope.interface/trunk/CHANGES.txt  2011-05-26 16:10:57 UTC (rev 121819)
 @@ -1,7 +1,12 @@
  ``zope.interface Changelog``
  
  
 +3.6.3 (unreleased)
 +--
  
 +- LP #570942:  Now correctly compare interfaces  from different modules but
 +  with the same names.
 +
  3.6.2 (2011-05-17)
  --
  
 
 Modified: zope.interface/trunk/src/zope/interface/interface.py
 ===
 --- zope.interface/trunk/src/zope/interface/interface.py  2011-05-26 
 11:27:21 UTC (rev 121818)
 +++ zope.interface/trunk/src/zope/interface/interface.py  2011-05-26 
 16:10:57 UTC (rev 121819)
 @@ -670,32 +670,42 @@
  sort before None.
  
  
 -if o1 == o2:
 -return 0
 -
  if o1 is None:
  return 1
  if o2 is None:
  return -1
  
 -n1 = (getattr(o1, '__name__', ''),
 -  getattr(getattr(o1,  '__module__', None), '__name__', ''))
 -n2 = (getattr(o2, '__name__', ''),
 -  getattr(getattr(o2,  '__module__', None), '__name__', ''))
 +n1 = (getattr(o1, '__name__', ''), getattr(o1,  '__module__', ''))
 +n2 = (getattr(o2, '__name__', ''), getattr(o2,  '__module__', ''))
  
 +# This spelling works under Python3, which doesn't have cmp().
  return (n1  n2) - (n1  n2)
  
 +def __eq__(self, other):
 +c = self.__cmp(self, other)
 +return c == 0
 +
 +def __ne__(self, other):
 +c = self.__cmp(self, other)
 +return c != 0
 +
  def __lt__(self, other):
  c = self.__cmp(self, other)
 -#print '', self, other, c  0, c
  return c  0
  
 +def __le__(self, other):
 +c = self.__cmp(self, other)
 +return c = 0
 +
  def __gt__(self, other):
  c = self.__cmp(self, other)
 -#print '', self, other, c  0, c
  return c  0
  
 +def __ge__(self, other):
 +c = self.__cmp(self, other)
 +return c = 0
  
 +
  Interface = InterfaceClass(Interface, __module__ = 'zope.interface')
  
  class Attribute(Element):
 
 Modified: zope.interface/trunk/src/zope/interface/tests/test_interface.py
 

Re: [Zope-dev] zope-tests - FAILED: 17, OK: 91

2011-06-08 Thread Gediminas Paulauskas
2011/5/25 Gediminas Paulauskas mene...@pov.lt:
 2011/5/25 Marius Gedminas mar...@gedmin.as:
 On Wed, May 25, 2011 at 09:18:46AM -0400, Tres Seaver wrote:
  [3]    FAILED  Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx
         https://mail.zope.org/pipermail/zope-tests/2011-May/041867.html

 The is an FTP test failure, similar to others which have showed up::

 -- $ -
 Failure in test testHELP (zope.server.ftp.tests.test_ftpserver.Tests)
 Traceback (most recent call last):
   File
 /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
 line 260, in run
     testMethod()
   File
 /Users/buildslave/.buildout/eggs/zope.server-3.6.2-py2.5.egg/zope/server/ftp/tests/test_ftpserver.py,
 line 278, in testHELP
     self.assertEqual(self.execute('HELP', 1), result)
   File
 /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
 line 334, 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'
 -- $ -

 I have no idea why this failure is only occasionaly, and only on OS/X.

 I had a theory and proposed a possible fix a while ago, but had no way
 of testing it:
 https://mail.zope.org/pipermail/zope-dev/2010-December/042138.html

 I have tested this and committed an equivalent patch:

 http://zope3.pov.lt/trac/changeset/121089/zope.server/trunk

 This was released recently as zope.server 3.8.3 (that has a new test
 failing on Python  2.6)

I have released the fix for Python  2.6 as 3.8.4.

 Have to backport to 3.6 branch for ZTK 1.0... and make new bugfix release

Branch created, minor fixes backported, including this testHELP
failure, and released as 3.6.3:

http://zope3.pov.lt/trac/log/zope.server/branches/3.6

-- 
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-tests - FAILED: 17, OK: 91

2011-05-25 Thread Gediminas Paulauskas
2011/5/25 Marius Gedminas mar...@gedmin.as:
 On Wed, May 25, 2011 at 09:18:46AM -0400, Tres Seaver wrote:
  [3]    FAILED  Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx
         https://mail.zope.org/pipermail/zope-tests/2011-May/041867.html

 The is an FTP test failure, similar to others which have showed up::

 -- $ -
 Failure in test testHELP (zope.server.ftp.tests.test_ftpserver.Tests)
 Traceback (most recent call last):
   File
 /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
 line 260, in run
     testMethod()
   File
 /Users/buildslave/.buildout/eggs/zope.server-3.6.2-py2.5.egg/zope/server/ftp/tests/test_ftpserver.py,
 line 278, in testHELP
     self.assertEqual(self.execute('HELP', 1), result)
   File
 /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
 line 334, 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'
 -- $ -

 I have no idea why this failure is only occasionaly, and only on OS/X.

 I had a theory and proposed a possible fix a while ago, but had no way
 of testing it:
 https://mail.zope.org/pipermail/zope-dev/2010-December/042138.html

I have tested this and committed an equivalent patch:

http://zope3.pov.lt/trac/changeset/121089/zope.server/trunk

This was released recently as zope.server 3.8.3 (that has a new test
failing on Python  2.6)

Have to backport to 3.6 branch for ZTK 1.0... and make new bugfix release

-- 
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-tests - FAILED: 18, OK: 79, UNKNOWN: 1

2011-05-23 Thread Gediminas Paulauskas
2011/5/23 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1


 [5]    UNKNOWN UNKNOWN : Zope-2.12 Python-2.6.6 : Linux
        https://mail.zope.org/pipermail/zope-tests/2011-May/041640.html

 This is a PyPI unreachable build failure.


 [6]    FAILED  Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
        https://mail.zope.org/pipermail/zope-tests/2011-May/041648.html


 [7]    FAILED  Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
        https://mail.zope.org/pipermail/zope-tests/2011-May/041650.html

 The segfault-on-exit which I can't reproduce on ubuntu64.



 [15]   FAILED  winbot / ztk_dev py_254_win32
        https://mail.zope.org/pipermail/zope-tests/2011-May/041691.html


 [16]   FAILED  winbot / ztk_dev py_265_win32
        https://mail.zope.org/pipermail/zope-tests/2011-May/041692.html


 [17]   FAILED  winbot / ztk_dev py_265_win64
        https://mail.zope.org/pipermail/zope-tests/2011-May/041693.html


 [18]   FAILED  winbot / ztk_dev py_270_win32
        https://mail.zope.org/pipermail/zope-tests/2011-May/041694.html


 [19]   FAILED  winbot / ztk_dev py_270_win64
        https://mail.zope.org/pipermail/zope-tests/2011-May/041695.html


 In each of these, he buildout fails (silently) while trying to check out
 code from SVN:

  mr.developer: svn: Can't create tunnel: The system cannot find the file
 specified.

buildbot tries to checkout from svn+ssh, because sources were moved to
separate files, ztk-sources.cfg and zopeapp-sources.cfg [1], and
buildbot does not remove ssh+ from source urls in those files.

[1] 
http://zope3.pov.lt/trac/changeset?new=121748%40zopetoolkit%2Ftrunkold=121746%40zopetoolkit%2Ftrunk

-- 
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 )


[Zope-dev] zope.security test failure on python2.7

2011-05-18 Thread Gediminas Paulauskas
2010/10/27 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 10/27/2010 07:58 AM, Zope Tests Summarizer wrote:
...
 Subject: FAILED : Zope Buildbot / zopetoolkit-py2.7 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Wed Oct 27 04:49:22 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/022426.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-py2.7 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Wed Oct 27 04:49:43 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/022427.html

 Our failures now seem to be all on Python 2.7 (progress, of a sort).
 Many of them fail due to the following attempt to use a proxy as the
 target of a weakref:

 - - % -
 File
 /home/zope/.buildout/eggs/zope.security-3.7.4-py2.7-linux-i686.egg/zope/security/tests/test_standard_checkers.py,
 line 509, in zope.security.tests.test_standard_checkers.test_ABCMeta
 Failed example:
    issubclass(PBar, Foo)
 Exception raised:
    Traceback (most recent call last):
      File /usr/lib/python2.7/doctest.py, line 1253, in __run
        compileflags, 1) in test.globs
      File doctest
 zope.security.tests.test_standard_checkers.test_ABCMeta[6], line 1, in
 module
        issubclass(PBar, Foo)
      File /usr/lib/python2.7/abc.py, line 151, in __subclasscheck__
        if subclass in cls._abc_cache:
      File /usr/lib/python2.7/_weakrefset.py, line 69, in __contains__
        return ref(item) in self.data
    TypeError: cannot create weak reference to
 'zope.security._proxy._Proxy' object

  Ran 124 tests with 1 failures and 0 errors in 0.433 seconds.
 Tearing down left over layers:
  Tear down zope.testrunner.layer.UnitTests in 0.000 seconds.
 - - % -

 Observations:

 - - Proxies can't be weakref targets under either Python 2.6 or 2.7.

 - - Under Python 2.7, the ABCMeta._abc_cache involved in the traceback
  is being morphed from a normal set (per the __new__ of the metaclass)
  to a _weakrefset.WeakSet.  Such sets cannot hold non-weakref-target
  objects.

I investigated this issue today, and committed a fix
http://zope3.pov.lt/trac/changeset/121714

It removes a check issubclass(PBar, Foo), where PBar is a proxy of class Bar.

This worked in Python 2.6, but not in Python 2.7 anymore because ABC
implementation was changed to use a WeakSet instead of set for the
cache, and _Proxy objects cannot be ref'ed. However, other objects
cannot be ref'ed either, the first argument to issubclass has to be a
type (see http://bugs.python.org/issue10569).

http://docs.zope.org/zopetoolkit/releases/overview-1.1.html#python-versions
links to http://bugs.python.org/issue10360 as the underlying problem.
I have applied the patch, but the test fails in the same place with a
different stacktrace:

File 
/home/menesis/.buildout/eggs/zope.security-3.8.1-py2.7-linux-i686.egg/zope/security/tests/test_standard_checkers.py,
line 509, in zope.security.tests.test_standard_checkers.test_ABCMeta
Failed example:
issubclass(PBar, Foo)
Exception raised:
Traceback (most recent call last):
  File /usr/lib/python2.7/doctest.py, line 1254, in __run
compileflags, 1) in test.globs
  File doctest
zope.security.tests.test_standard_checkers.test_ABCMeta[6], line 1,
in module
issubclass(PBar, Foo)
  File /home/menesis/src/zope/zopetoolkit-1.1/python/lib/python2.7/abc.py,
line 171, in __subclasscheck__
cls._abc_cache.add(subclass)
  File 
/home/menesis/src/zope/zopetoolkit-1.1/python/lib/python2.7/_weakrefset.py,
line 84, in add
self.data.add(ref(item, self._remove))
TypeError: cannot create weak reference to
'zope.security._proxy._Proxy' object

So the patch, that we were waiting for to be released with python
2.7.2, does not help.

So I removed the (incorrect) issubclass call, and the rest of the test
passes, showing that ABC checker works correctly. Even if it would be
good that issubclass worked, I think that mixing ABCs and Zope
interfaces is very unlikely anyway.

But having one test that is known to fail, and consequently not test
all of ZTK at all is wrong. Now ZTK builders on python 2.7 can be
added/enabled again. Please do so.

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-tests - FAILED: 8, OK: 55

2011-04-27 Thread Gediminas Paulauskas
 [1]    FAILED  Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32
       https://mail.zope.org/pipermail/zope-tests/2011-April/039122.html

I have committed a fix for this failure, but it was not released, and
this buildbot tests eggs.

http://zope3.pov.lt/trac/changeset/121089/zope.server

 [2]    FAILED  winbot / z3c.coverage_py_265_32
       https://mail.zope.org/pipermail/zope-tests/2011-April/039137.html


 [3]    FAILED  winbot / z3c.rml_py_265_32
       https://mail.zope.org/pipermail/zope-tests/2011-April/039135.html

I have committed several fixes for z3c.rml, but I cannot debug the
Broken pipe on windows. Maybe a path to gs (Ghostscript) is incorrect.
If someone with windows could investigate this long-standing failure,
would be very helpful.

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 Tests: 109 OK, 24 Failed, 4 Unknown

2011-03-31 Thread Gediminas Paulauskas
2011/3/25 Gediminas Paulauskas mene...@pov.lt:
 Buildout tries to download ClientForm from sourceforge.net and seems to get 
 a broken content-length header.
 I see the same problem when using distutils 0.6.14 since the last 3 or 4 
 days.
 But when I use wget the header seems to be correct or wget is smart enough 
 to fix it.

 ClientForm 0.2.10 (and mechanize 0.1.11) downloads do not exhibit this
 problem. I have updated zope.release to these versions to make
 buildbot green.

No, this did not help to fix the 3.4 KGS, newer versions also failed
to download.
___
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: 109 OK, 24 Failed, 4 Unknown

2011-03-31 Thread Gediminas Paulauskas
2011/3/23 Laurence Rowe l...@lrowe.co.uk:
 On 23 March 2011 14:43, Tres Seaver tsea...@palladion.com wrote:
 Multiple 'Content-Length' headers is definitely a Bad Thing.  I filed a
 bug, which Mark Ramm has promised to escalate:

  https://sourceforge.net/apps/trac/sourceforge/ticket/18486

 I have a patch for setuptools which works around it:

  http://bugs.python.org/setuptools/issue123

 I'm not sure how to work around the issue at the moment.

 I always add the following to my buildout.cfg to avoid problems with
 random third party servers:

 allow-hosts =
    *.python.org
    *.plone.org
    launchpad.net

 (launchpad.net is there only for mocker which does not have a pypi release).

I have added the following sites to allow-hosts for SchoolTool, that
needs Sphinx, Pygments, PIL, reportlab, pyPdf, Paste.

allow-hosts =
buildout.org
code.google.com
effbot.org
*.googlecode.com
pybrary.net
pygments.org
*.python.org
pythonpaste.org
*.pythonware.com
*.pocoo.org
reportlab.com
*.repoze.org
*.schooltool.org

Not all sites are needed, but why block projects official downloads?

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 Tests: 109 OK, 24 Failed, 4 Unknown

2011-03-25 Thread Gediminas Paulauskas
2011/3/23 Michael Howitz m...@gocept.com:
 Am 23.03.2011 um 12:57 schrieb Zope Tests Summarizer:
 Test failures
 -
 [...]
 Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux
 From: buildbot at pov.lt
 Date: Tue Mar 22 22:26:52 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035953.html

 While:
  Installing test.
  Getting distribution for 'ClientForm==0.2.9'.

 An internal error occured due to a bug in either zc.buildout or in a
 recipe being used:
 Traceback (most recent call last):
  ...
  File 
 /var/lib/buildbot/slaves/zope-kgs/py2.4-32bit-linux/build/test/eggs/setuptools-0.6c11-py2.4.egg/setuptools/package_index.py,
  line 553, in _download_to
    size = int(headers[Content-Length])
 ValueError: invalid literal for int(): 102936, 102936

 Buildout tries to download ClientForm from sourceforge.net and seems to get a 
 broken content-length header.
 I see the same problem when using distutils 0.6.14 since the last 3 or 4 days.
 But when I use wget the header seems to be correct or wget is smart enough to 
 fix it.

ClientForm 0.2.10 (and mechanize 0.1.11) downloads do not exhibit this
problem. I have updated zope.release to these versions to make
buildbot green.

But this remains a problem for people who have extends =
http://download.zope.org/zope3.4/3.4.1/versions.cfg in their apps...

Let's hope sourceforge.net will fix the issue on their end.

Gediminas
http://zope3.pov.lt/
___
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: 73 OK, 12 Failed, 4 Unknown

2011-03-25 Thread Gediminas Paulauskas
2011/3/24 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 03/24/2011 07:57 AM, Zope Tests Summarizer wrote:

 Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux
 From: buildbot at pov.lt
 Date: Wed Mar 23 22:26:52 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036056.html

 IS there a 3.4 KGS doctor in the house?

I have tried to fix the 3.4 issues. Let's wait for tomorrow.

 Subject: FAILED : winbot / z3c.rml_py_265_32
 From: buildbot at winbot.zope.org
 Date: Wed Mar 23 22:40:00 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036057.html

 This package looks to be mostly Stephan Richter's work, with
 contributions from some of the Usual Suspects.

We use z3c.rml in SchoolTool and it works... Strange errors, though,
haven't investigated yet.

 Subject: UNKNOWN : Zope-2.13 Python-2.6.5 : Linux
 From: Zope Tests
 Date: Thu Mar 24 02:08:58 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036071.html

 Subject: UNKNOWN : Zope-2.13-alltests Python-2.6.5 : Linux
 From: Zope Tests
 Date: Thu Mar 24 02:10:58 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036072.html

 Subject: UNKNOWN : Zope-trunk Python-2.6.5 : Linux
 From: Zope Tests
 Date: Thu Mar 24 02:12:58 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036073.html

 Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux
 From: Zope Tests
 Date: Thu Mar 24 02:14:58 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036074.html

 These are all failures to download the 'mechanize' package, due to the
 SourceForge bug (multiple 'Content-Type' headers).  We can address via:

 - - Using setuptools-0.6c12dev-r88793.tar.gz (PJE has merged my
  workaround).

 - - Waiting for the SF guys to fix the bug,
  http://sourceforge.net/apps/trac/sourceforge/ticket/18486

 - - Blocking the buildouts from using SF, as suggested yesterday by adding
  'allow-hosts' to the buildout.cfg, as suggested by Laurence Rowe::

  allow-hosts =
    *.python.org

I do not touch Zope2, and none of the options is appealing. The last
one is simplest...

For Zope 3.4 the buildout.cfg is generated from template in zope.kgs
egg, did not want to make a release of it just to add a workaround.

But I discovered that latest bugfix releases, ClientForm 0.2.10 and
mechanize 0.1.11, do not manifest this problem. So the 4th workaround
is to upgrade them.

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 Tests: 29 OK, 15 Failed, 4 Unknown

2011-03-25 Thread Gediminas Paulauskas
2011/3/25 Zope Tests Summarizer zope-te...@epy.co.at:
 Summary of messages to the zope-tests list.
 Period Thu Mar 24 12:00:00 2011 UTC to Fri Mar 25 12:00:00 2011 UTC.
 There were 48 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 23 from 
 buildbot at winbot.zope.org, 8 from ccomb at free.fr, 5 from jdriessen at 
 thehealthagency.com.

 Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux
 From: buildbot at pov.lt
 Date: Thu Mar 24 22:01:49 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036104.html

 Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux
 From: buildbot at pov.lt
 Date: Thu Mar 24 22:14:00 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036105.html

 Subject: FAILED : Zope 3.4 Known Good Set / py2.5-64bit-linux
 From: buildbot at pov.lt
 Date: Thu Mar 24 23:01:44 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036107.html

 Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux
 From: buildbot at pov.lt
 Date: Thu Mar 24 23:10:30 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036108.html

 Subject: FAILED : Zope 3.4 KGS / Python2.4.6 64bit linux
 From: ccomb at free.fr
 Date: Fri Mar 25 01:00:44 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036113.html

 Subject: FAILED : Zope 3.4 KGS / Python2.5.5 64bit linux
 From: ccomb at free.fr
 Date: Fri Mar 25 01:01:22 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036114.html

Zope 3.4 KGS builds failed because python-dateutil 2.0 was released,
that supports only Python 3. I have pinned python-dateutil = 0.1.5 in
zope.release that should fix all these failures.

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 Tests: 68 OK, 34 Failed, 6 Unknown

2011-03-21 Thread Gediminas Paulauskas
2011/3/21 Zope Tests Summarizer zope-te...@epy.co.at:
 Summary of messages to the zope-tests list.
 Period Sun Mar 20 12:00:00 2011 UTC to Mon Mar 21 12:00:00 2011 UTC.
 There were 108 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 29 
 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 59 from jdriessen 
 at thehealthagency.com.


 Test failures
 -

 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 09:44:36 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035632.html

 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 09:44:59 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035633.html

 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 09:46:37 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035634.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 09:57:26 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035639.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 10:12:01 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035645.html

 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 13:05:48 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035646.html

 Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 13:10:43 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035649.html

 Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 13:12:19 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035650.html

 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:21:50 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035658.html

 Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:26:33 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035661.html

 Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:28:05 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035662.html

 Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:41:43 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035665.html

 Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:43:55 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035666.html

All of Zope2 test failures that I have looked at have been caused by r121036
http://zope3.pov.lt/trac/changeset/121036/Zope/trunk/src/ZServer that
adds support for IPv6 to ZServer.

It should work with ZConfig trunk, that also adds IPv6 support, but
has not been released
http://zope3.pov.lt/trac/changeset/116987/ZConfig/trunk

Please release ZConfig or unpin 2.8.0 from Zope trunk.

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win
 From: jdriessen at thehealthagency.com
 Date: Sun Mar 20 15:48:55 EDT 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035668.html

Many other failures were connection problems.

-- 
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 Tests: 83 OK, 31 Failed, 1 Unknown

2011-03-09 Thread Gediminas Paulauskas
2011/3/2 Hanno Schlichting ha...@hannosch.eu:
 On Wed, Mar 2, 2011 at 4:42 PM, Gediminas Paulauskas mene...@pov.lt wrote:
 zope.traversing = 3.13.1

 This bugfix has new requirements, at least

 zope.security = 3.8.0
 zope.browserresource = 3.12.0

 All three of them do the same - make it possible to include their zcml
 files directly.

 And these versions have been tested for a long time in ztk 1.0dev
 builders, so are good to go in.

 Unfortunately they are not good for ZTK 1.0.x. ZTK 1.0 uses
 zope.browserresource 3.10.3. It's 3.11.0 version introduces a
 completely new API that already required code and test changes on the
 Zope 2 level - making it likely to cause even further troubles in
 higher level frameworks or applications.

 I've rereleased zope.traversing 3.13.1 as 3.14.0 for ZTK 1.1 and
 rereleased 3.13.0 as 3.13.2 for ZTK 1.0.

If so, I have branched zope.browserresource/branches/3.10 for ZTK 1.0.


 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: 83 OK, 31 Failed, 1 Unknown

2011-03-02 Thread Gediminas Paulauskas
2011/3/2 Zope Tests Summarizer zope-te...@epy.co.at:
 Summary of messages to the zope-tests list.
 Period Tue Mar  1 12:00:00 2011 UTC to Wed Mar  2 12:00:00 2011 UTC.
 There were 115 messages: 8 from Zope Tests, 26 from buildbot at 
 winbot.zope.org, 11 from ccomb at free.fr, 70 from jdriessen at 
 thehealthagency.com.


 Test failures
 -

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 09:50:15 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033505.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 10:02:20 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033508.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:50:33 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033540.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:50:37 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033541.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:50:39 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033542.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:51:06 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033544.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:51:13 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033545.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:51:23 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033546.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:51:43 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033547.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:51:54 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033548.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 14:52:28 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033549.html

 Subject: FAILED : winbot / ztk_10 py_244_win32
 From: buildbot at winbot.zope.org
 Date: Tue Mar  1 15:57:01 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033556.html

 Subject: FAILED : winbot / ztk_10 py_254_win32
 From: buildbot at winbot.zope.org
 Date: Tue Mar  1 15:57:51 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033557.html

 Subject: FAILED : winbot / ztk_10 py_265_win32
 From: buildbot at winbot.zope.org
 Date: Tue Mar  1 15:58:31 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033558.html

 Subject: FAILED : winbot / ztk_10 py_265_win64
 From: buildbot at winbot.zope.org
 Date: Tue Mar  1 15:58:59 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033559.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 18:40:24 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033572.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 18:41:26 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033573.html

 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx
 From: jdriessen at thehealthagency.com
 Date: Tue Mar  1 18:42:54 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033574.html

 Subject: FAILED : ZTK 1.0 / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Tue Mar  1 19:02:18 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033577.html

 Subject: FAILED : ZTK 1.0 / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Tue Mar  1 19:02:26 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033578.html

 Subject: FAILED : ZTK 1.0 / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Tue Mar  1 19:02:34 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033579.html

Some of the new failures, resulting in

The version, 3.7.4, is not consistent with the requirement,
'zope.security[zcml]=3.8'.
While:
 Installing test-ztk.
Error: Bad version 3.7.4

are caused by recent change to ztk 1.0 branch

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

2011-02-04 Thread Gediminas Paulauskas
2011/2/4 Zope Tests Summarizer zope-te...@epy.co.at:
 Summary of messages to the zope-tests list.
 Period Thu Feb  3 12:00:00 2011 UTC to Fri Feb  4 12:00:00 2011 UTC.
 There were 56 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 21 from 
 buildbot at winbot.zope.org, 11 from ccomb at free.fr, 12 from jdriessen at 
 thehealthagency.com.


 Test failures
 -

 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Feb  3 21:29:54 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/030912.html

 Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Feb  3 21:30:03 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/030913.html

 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Thu Feb  3 21:30:04 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/030914.html

I have created a zope.app.wsgi/branches/3.9 and switched ztk 1.0dev to
it. This failure will be fixed.

But then I see that some other modules (most notably, zope.traversing
3.13.1) that have trunk in ztk 1.0 require zope.security[zcml]=3.8
but we only have 3.7.4. It looks like a harmless change, can
zope.security be upgraded in the stable branch?
___
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: 81 OK, 9 Failed, 2 Unknown

2011-01-31 Thread Gediminas Paulauskas
2011/1/31 Marius Gedminas mar...@gedmin.as:
 On Mon, Jan 31, 2011 at 12:58:05PM +0100, Zope Tests Summarizer wrote:
 Test failures
 -

 Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux
 From: buildbot at pov.lt
 Date: Sun Jan 30 21:11:27 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030530.html

 Subject: FAILED : Zope 3.4 Known Good Set / py2.5-64bit-linux
 From: buildbot at pov.lt
 Date: Sun Jan 30 22:10:42 EST 2011
 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030539.html

 These started happening because we upgraded virtualenv on that box (from
 1.3.3 to 1.4.5).  I can't downgrade because a different buildbot
 slave (for our internal product) needs the new virtualenv.

I have added a --setuptools option to virtualenv to get the old
behaviour back (not print install_dir like distribute does). This will
make the test pass tomorrow.

 Ideally I'd like to fix zc.zope3recipes to work with modern tool
 versions, if I can find the time.

I checked zc.zope3recipes, and even in trunk tests fail when either
zc.buildout = 1.5 or distribute is used.

Only the tests need to be changed, they check too much of output of buildout.

-- 
Gediminas Paulauskas
___
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] ZPL 2.0 usage and other license problems

2010-12-03 Thread Gediminas Paulauskas
Hello,

I am packaging Zope Toolkit for Ubuntu, but archive admins have
noticed that some files have Zope Public License, Version 2.0 in
their headers. I guess this is unintentional, but now I have to find
such files and specify their license separately. Can I simply change
the version number to 2.1 and commit to the Zope repository? The
affected files that I care about are attached.

zope.server/src/zope/server/http/tests/test_wsgiserver.py even
specifies ZPL 1.1, that might be incompatible with 2.1.

At the same time, LICENSE.txt and COPYRIGHT.txt files that are still
missing in many packages could be added, using zope.repositorypolicy
scripts.

While investigating this, I noticed that there is only the ZPL 2.0 at
http://www.opensource.org/licenses/zpl.php that is correctly
categorized as Non-reusable in
http://www.opensource.org/licenses/category . The ZPL 2.1 is now
reusable, but it is not visible at opensource.org, and therefore its
claim This license has been certified as open source. is not true.

Two more packages have other copyright problems:

zope.pagetemplate contains non-free files. See
https://bugs.launchpad.net/zope.pagetemplate/+bug/607228

zope.structuredtext contains some files that are (C) Digital Creations
and link to a non-existing COPYRIGHT.html. This makes them non-free as
well.

Who can fix the mentioned problems?

-- 
Gediminas Paulauskas
zc.buildout/src/zc/buildout/rmtree.py
zc.buildout/src/zc/buildout/tests.py
zc.buildout/src/zc/buildout/testselectingpython.py
zc.buildout/src/zc/buildout/testing.py
zc.lockfile/src/zc/lockfile/tests.py
zope.app.authentication/src/zope/app/authentication/password.py
zope.app.authentication/src/zope/app/authentication/idpicker.py
zope.app.catalog/src/zope/app/catalog/browser/catalog.py
zope.app.catalog/src/zope/app/catalog/keyword.py
zope.app.catalog/src/zope/app/catalog/field.py
zope.app.catalog/src/zope/app/catalog/interfaces.py
zope.app.catalog/src/zope/app/catalog/text.py
zope.app.catalog/src/zope/app/catalog/tests.py
zope.app.catalog/src/zope/app/catalog/attribute.py
zope.app.catalog/src/zope/app/catalog/catalog.py
zope.app.component/src/zope/app/component/browser/tests.py
zope.app.form/src/zope/app/form/browser/source.py
zope.app.intid/src/zope/app/intid/browser/tests.py
zope.applicationcontrol/test.py
zope.app.publication/src/zope/app/publication/tests/test_functional.py
zope.app.publication/src/zope/app/publication/tests/test_proxycontrol.py
zope.app.session/src/zope/app/session/http.py
zope.app.testing/src/zope/app/testing/tests.py
zope.app.testing/src/zope/app/testing/dochttp.py
zope.app.wsgi/src/zope/app/wsgi/tests.py
zope.app.zptpage/src/zope/app/zptpage/textindex/tests.py
zope.app.zptpage/src/zope/app/zptpage/textindex/zptpage.py
zope.cachedescriptors/src/zope/cachedescriptors/tests.py
zope.formlib/src/zope/formlib/tests/test_source.py
zope.formlib/src/zope/formlib/source.py
zope.i18n/src/zope/i18n/tests/test_testmessagecatalog.py
zope.i18n/src/zope/i18n/tests/test.py
zope.i18n/src/zope/i18n/locales/tests/test_fallbackcollator.py
zope.interface/src/zope/interface/adapter.py
zope.interface/src/zope/interface/common/tests/test_import_interfaces.py
zope.password/src/zope/password/password.py
zope.publisher/src/zope/publisher/tests/test_xmlrpc.py
zope.publisher/src/zope/publisher/tests/test_paste.py
zope.security/src/zope/security/_zope_security_checker.c
zope.security/src/zope/security/untrustedpython/tests.py
zope.security/src/zope/security/__init__.py
zope.securitypolicy/src/zope/securitypolicy/grantinfo.py
zope.session/src/zope/session/http.py
zope.testbrowser/src/zope/testbrowser/tests.py
zope.testing/src/zope/testing/renormalizing/__init__.py
zope.testing/src/zope/testing/testrunner/testrunner-ex-pp-products/sampletests.py
zope.testing/src/zope/testing/testrunner/testrunner-ex-pp-products/more/sampletests.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/samplelayers.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sampletestsf.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/pledge.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sample11/sampletests.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests_ntd.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletestsf.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests_none_suite.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test_one.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test112.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test122.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test1.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test12.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test11.py
zope.testing/src/zope/testing/testrunner/testrunner-ex/sample1/sampletests/test121.py

Re: [Zope-dev] (re)moving browser subpackage from zc.catalog?

2010-10-05 Thread Gediminas Paulauskas
I would like the ZMI views and zope.app dependencies be removed as
well. I think I remember even some tests fail with ztk1.0?

2010/10/5, Jan-Wijbrand Kolman janwijbr...@gmail.com:
 Hi,

 Today I fixed a small bug in zc.catalog (the ftesting.zcml depended on a
 permission name that has been removed from zope.dublincore). This made
 me realize that zc.catalog contains ZMI code in the browser subpackage.

 Are people still using this ZMI code from zc.catalog? Would it be an
 idea to move the ZMI code out of the package (a bit similar to how
 various zope.app.* package have been refactored)? It would make
 maintaining this package in respect to the ZTK easier.

 Kind 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 )


Re: [Zope-dev] (re)moving browser subpackage from zc.catalog?

2010-10-05 Thread Gediminas Paulauskas
2010/10/5, Jan-Wijbrand Kolman janwijbr...@gmail.com:
 Hi,

 Today I fixed a small bug in zc.catalog (the ftesting.zcml depended on a
 permission name that has been removed from zope.dublincore). This made
 me realize that zc.catalog contains ZMI code in the browser subpackage.

 Are people still using this ZMI code from zc.catalog? Would it be an
 idea to move the ZMI code out of the package (a bit similar to how
 various zope.app.* package have been refactored)? It would make
 maintaining this package in respect to the ZTK easier.

 Kind 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 )


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

2010-09-28 Thread Gediminas Paulauskas
2010/9/28 Hanno Schlichting ha...@hannosch.eu:
 Hello.

 On behalf of the Zope Toolkit release team and the Zope community, I'm
 happy to announce the second release candidate of the Zope Toolkit
 version 1.0.

 Compared to the first release candiate we solved all the problems with
 packages having test dependencies on other deprecated packages.

 You can read more about the release at
 http://docs.zope.org/zopetoolkit/releases/overview-1.0c2.html. The
 first ZTK release supports all of Python 2.4, 2.5 and 2.6.

 To use the ZTK release, you can use:

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

The 1.0c2 tag has been copied from trunk, but it was supposed to be
made from the 1.0 branch.

The release overview also mentions 1.1a1 and has versions from trunk.

 This release focuses on cleaning up the ztk and zopeapp package lists
 by deprecating packages that are not used by any of the frameworks
 that use the ZTK.

This note applies only to trunk. Only one package was deprecated in 1.0 branch.

 We'd encourage everyone to test this release and notify us of any
 problems you find. Depending on the feedback we get we'll release a
 final release in the next two weeks.

 We post our meeting notes at
 http://docs.zope.org/zopetoolkit/releaseteam/index.html. Feel free to
 start discussing with us on this mailing list.

 Kind regards,
 Hanno Schlichting
___
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: 34 OK, 13 Failed, 3 Unknown

2010-09-22 Thread Gediminas Paulauskas
2010/9/22 Michael Howitz m...@gocept.com:
 Am 22.09.2010 um 13:58 schrieb Zope Tests Summarizer:
 Summary of messages to the zope-tests list.
 Period Tue Sep 21 12:00:00 2010 UTC to Wed Sep 22 12:00:00 2010 UTC.
 There were 50 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 21 
 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 8 from jdriessen 
 at thehealthagency.com.

 Test failures
 -
 [...]
 Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
 From: ccomb at free.fr
 Date: Tue Sep 21 23:15:02 EDT 2010
 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020388.html

 This failure is due to missing zope.generations which is needed by 
 zope.app.generations 3.7. So I switched to a maintenance branch of 
 zope.app.generations.

I would add zope.generations rather than switch to maintenance branch.
The independent zope.generations is what contains the code to use by
applications.

Nothing else apart from the split has changed, compatibility imports
and zcml are left in place, so it should be safe to have the two
packages in ZTK 1.0.
___
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 Gediminas Paulauskas
2010/9/21 Michael Howitz m...@gocept.com:
 Am 20.09.2010 um 17:22 schrieb Tres Seaver:
 [...]
 Right, and we should be adding zope.testrunner to the ZTK trunk.

 Done in r116694. But this change might lead to other problems: When updating 
 to zope.testing 3.10.0 in ztk-versions.cfg I get the following error when 
 running buildout:

 The version, 3.10.0, is not consistent with the requirement, 
 'zope.testing=3.6.0,3.10.0'.
 While:
  Installing.
  Getting section test-ztk.
  Initializing section test-ztk.
  Installing recipe z3c.recipe.compattest.
 Error: Bad version 3.10.0

Need to update zc.recipe.testrunner to 1.3.0 that is compatible with
zope.testing 3.10. The patch doing that is attached.

Gediminas
Index: ztk-versions.cfg
===
--- ztk-versions.cfg	(revision 116706)
+++ ztk-versions.cfg	(working copy)
@@ -62,7 +62,8 @@
 zope.structuredtext = 3.5.0
 zope.tal = 3.5.2
 zope.tales = 3.5.1
-zope.testing = 3.9.5
+zope.testing = 3.10.0
+zope.testrunner = 4.0.0b5
 zope.traversing = 3.13
 zope.viewlet = 3.7.2
 
@@ -79,17 +80,19 @@
 py = 1.3.2
 Pygments = 1.3.1
 python-gettext = 1.0
+python-subunit = 0.0.6
 pytz = 2010l
 RestrictedPython = 3.6.0
 setuptools = 0.6c11
 Sphinx = 1.0.3
+testtools = 0.9.6
 transaction = 1.1.0
 z3c.recipe.sphinxdoc = 0.0.8
 zc.buildout = 1.4.4
 zc.lockfile = 1.0.0
 ZConfig = 2.8.0
 zc.recipe.egg = 1.2.2
-zc.recipe.testrunner = 1.2.1
+zc.recipe.testrunner = 1.3.0
 zc.resourcelibrary = 1.3.1
 zdaemon = 2.0.4
 ZODB3 = 3.9.5
___
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 Gediminas Paulauskas
2010/9/17 Christophe Combelles cc...@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.

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.

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.

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] z3c.form release

2010-05-17 Thread Gediminas Paulauskas
2010/5/17 Wichert Akkerman wich...@wiggy.net:
 On 5/15/10 09:59 , Martin Aspeli wrote:


 On 15 May 2010 15:39, Wichert Akkerman wich...@wiggy.net
 mailto:wich...@wiggy.net wrote:

     On 5/10/10 17:24 , Wichert Akkerman wrote:
       I fixed a few issues in z3c.form today. Can anyone make a 2.3.4
     release?


     Since I got no reaction I'll repeat this request: can someone please
     make a new z3c.form release? Looking at the pypi page there is no
     shortage of people with the ability to do so..


 And now you're one of those people. ;-)'

 Thanks, I've kicked out 2.3.4.

Not sure how the http://pypi.python.org/pypi/z3c.form page looked
before, but for some reason not only it is not rendered as ReST
content, but is double-escaped (i.e. full of gt; strings) as well.


 Can you update whatever bit on good-py pins z3c.form to 2.3.3 to 2.3.4?
 I couldn't find where that was coming in from.

 Wichert.
 ___
 Zope-Dev maillist  -  zope-...@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] No license distributed with sources

2010-02-08 Thread Gediminas Paulauskas
Hello Zope Developers,

I am packaging many Zope libraries for Ubuntu. But my packages were
rejected by archive admin because the source tarballs do not satisfy
the inclusion requirements.

From https://wiki.ubuntu.com/PackagingGuide/Basic#Copyright :

  * The upstream tarball must contain verbatim copies of all licenses
that are used by the files in the tarball. References to URLs or paths
to system files (such as /usr/share/common-licenses/) are not
sufficient. The license(s) must accompany the source code.

Every file under the ZPL has a sentence A copy of the ZPL should
accompany this distribution. in it's header. But that's not the case.
Very few packages ship a ZopePublicLicense.txt in their source.

Reading the ZPL, its first condition is:

1. Redistributions in source code must retain the
   accompanying copyright notice, this list of conditions,
   and the following disclaimer.

Since this condition is not met, such packages cannot be legally distributed.

Who will add a copy of the license to each package in Zope SVN? When?
___
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] No license distributed with sources

2010-02-08 Thread Gediminas Paulauskas
2010/2/8 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Gediminas Paulauskas wrote:
 Hello Zope Developers,

 I am packaging many Zope libraries for Ubuntu. But my packages were
 rejected by archive admin because the source tarballs do not satisfy
 the inclusion requirements.

From https://wiki.ubuntu.com/PackagingGuide/Basic#Copyright :

   * The upstream tarball must contain verbatim copies of all licenses
 that are used by the files in the tarball. References to URLs or paths
 to system files (such as /usr/share/common-licenses/) are not
 sufficient. The license(s) must accompany the source code.

 Every file under the ZPL has a sentence A copy of the ZPL should
 accompany this distribution. in it's header. But that's not the case.
 Very few packages ship a ZopePublicLicense.txt in their source.

 Reading the ZPL, its first condition is:

 1. Redistributions in source code must retain the
    accompanying copyright notice, this list of conditions,
    and the following disclaimer.

 Since this condition is not met, such packages cannot be legally distributed.

 Who will add a copy of the license to each package in Zope SVN? When?

  $ wget \
   http://pypi.python.org/packages/source/Z/Zope2/Zope2-2.12.3.tar.gz
  $ tar tzf Zope2-2.12.3.tar.gz | grep -i license
  Zope2-2.12.3/src/ZServer/medusa/dist/license.html
  Zope2-2.12.3/ZopePublicLicense.txt

I am talking about the packages making up the ZTK and ZopeApp. I am
packaging each of them separately -- see
http://revu.ubuntuwire.com/u/menesis . Each one, even the smallest
ones like zope.size, zope.filerepresentation, zope.app.zcmlfiles has
to contain a license in their source tarballs.
___
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] No license distributed with sources

2010-02-08 Thread Gediminas Paulauskas
2010/2/8 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Gediminas Paulauskas wrote:
 2010/2/8 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Gediminas Paulauskas wrote:
 Hello Zope Developers,

 I am packaging many Zope libraries for Ubuntu. But my packages were
 rejected by archive admin because the source tarballs do not satisfy
 the inclusion requirements.

 From https://wiki.ubuntu.com/PackagingGuide/Basic#Copyright :

   * The upstream tarball must contain verbatim copies of all licenses
 that are used by the files in the tarball. References to URLs or paths
 to system files (such as /usr/share/common-licenses/) are not
 sufficient. The license(s) must accompany the source code.

 Every file under the ZPL has a sentence A copy of the ZPL should
 accompany this distribution. in it's header. But that's not the case.
 Very few packages ship a ZopePublicLicense.txt in their source.

 Reading the ZPL, its first condition is:

 1. Redistributions in source code must retain the
    accompanying copyright notice, this list of conditions,
    and the following disclaimer.

 Since this condition is not met, such packages cannot be legally 
 distributed.

 Who will add a copy of the license to each package in Zope SVN? When?
  $ wget \
   http://pypi.python.org/packages/source/Z/Zope2/Zope2-2.12.3.tar.gz
  $ tar tzf Zope2-2.12.3.tar.gz | grep -i license
  Zope2-2.12.3/src/ZServer/medusa/dist/license.html
  Zope2-2.12.3/ZopePublicLicense.txt

 I am talking about the packages making up the ZTK and ZopeApp. I am
 packaging each of them separately -- see
 http://revu.ubuntuwire.com/u/menesis . Each one, even the smallest
 ones like zope.size, zope.filerepresentation, zope.app.zcmlfiles has
 to contain a license in their source tarballs.

 I've got no objections to having that file copied to each of those
 packages and new releases made, but it isn't my itch to scratch.

  $ for pkg in $(cat list_of_package_branches_needing_zpl.txt); do \
     svn cp -m Add ZPL text $ZSVN/Zope2/trunk/ZopePublicLicense.txt \
                              $ZSVN/$pkg; done

 should be a start.  Making new releases and uploading them is left as an
 exercise for the reader.  I will note that Christian Theune is about to
 run a big script updating all comment headers to indicate copyright
 assignment to the Zope Foundation:  perhaps you would coordinate with
 him, as he will likely be doing a release-and-upload-geddon after that
 change.

I know that copyright is about to be changed to Zope Foundation. A
perfect time to ensure the license is there.

 In the mean time, you could patch the file in via your debian/ control
 stuff, I guess.  The Ubuntu / Debian interpretation of legality of
 distribution is not controlling outside their universes, I think.

Yes, I was told that patching the source to add the file would be
enough to get them accepted.
Provided that I ask the upstream developers to do that in the future for real.
___
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] upload zope.app.exception to pypi

2010-01-08 Thread Gediminas Paulauskas
2010/1/4 Jan-Wijbrand Kolman janwijbr...@gmail.com:
 Baiju M mba...@zeomega.com wrote:
 On Mon, Jan 4, 2010 at 6:32 PM, Jan-Wijbrand Kolman
 janwijbr...@gmail.com wrote:
 Would any of the pypi owners of zope.app.exception be so kind to
 upload the 3.6.0 release to the package index? I see this package has
 been tagged already a while ago.

 I think this newer version should also be included in the ZTK versions
 list, as this version will import the correct ISystemErrorView
 interface from zope.browser.

 I have added jw as owner of this package.

 Ok, thank you.

 BTW, I am getting this error from 3.6.0 branch.:

 Me too.

 $ ./bin/test
 /opt/baiju/wa/z3hello/eggs/zope.testing-3.8.6-py2.6.egg/zope/testing/
 testrunner/debug.py:23:
 DeprecationWarning: zope.testing.doctest is deprecated in favour of
 the Python standard library doctest module
   from zope.testing import doctest
 Test-module import failures:

 Module: zope.app.exception.browser.tests.test_unauthorized

 Traceback (most recent call last):
   File /tmp/zope.app.exception/src/zope/app/exception/browser/tests/
 test_unauthorized.py,
 line 20, in module
     import zope.app.pagetemplate.namedtemplate
   File /opt/baiju/wa/z3hello/eggs/zope.app.pagetemplate-3.10.0-py2.6.egg/
 zope/app/pagetemplate/namedtemplate.py,
 line 20, in module
     from zope.browerpage.namedtemplate import implementation
 ImportError: No module named browerpage.namedtemplate

 As it turns out, since the release of zope.app.exception 3.6.0 namedtemplate
 has again been moved. It is now in zope.browserpage. However, zope.browserpage
 is not required yet by zope.app.exception.

 I'll make it require zope.browserpage and release (and upload!)
 zope.app.exception 3.7.0.

Could you upload 3.6.0 as it was anyway, the ISystemErrorView move
would be useful for me since I run SchoolTool on an older/custom KGS.


 Would that be OK?

 regards,
 jw


 ___
 Zope-Dev maillist  -  zope-...@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] New Zope 3 name: BlueBream

2010-01-05 Thread Gediminas Paulauskas
2010/1/5 Martin Aspeli optilude+li...@gmail.com:
 Andreas Jung wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Baiju M wrote:
 Hi All, I am proposing to call Zope 3 - the web frame work as
 BlueBream.  The main use for name is documentation. But the
 package named bluebream will not provide any part of framework
 code by itself. All the framework code will be in zope and
 zope.app namespaces.
 I associate blueberry bagels with cream cheese when reading the name
 Bluebream. Sorry but this name is pointless and does not solve any issue
 - - it just introduces some more confusion.

 I think if there are people interested in the web development framework
 previously known as Zope 3 - and it seem that there is - we'll need to
 call it something. I think continuing to call it Zope 3 is just
 confusing, given that we've factored the ZTK out of Zope 3, and we've
 spent ages saying that Zope 3 is part of Zope 2 and Zope 3 is part of
 Grok. That message was confusing before, and the history since is
 making it more confusing still.

If we released Zope 3 the web framework as version 3.5, little would
change for existing Zope 3 users since it still includes all zope.app
packages with backward compatibility imports. Wasn't this the plan
last year? I see no more confusion than was before, only less. The
reasons mentioned here are now false, because Zope 3.5 is based on
ZTK, Zope 2.12 is based on ZTK, and Grok is based on ZTK. Explanations
written at http://download.zope.org/zope3.4/ are still true, and after
renaming some occurrences of Zope 3 to ZTK, Zope 3.5 KGS would be
the same Zope 3 thing as Zope 3.4 was.

I am a Zope 3 developer for two large apps but I don't care about the fish.

-- 
Gediminas Paulauskas
Programmer at POV
___
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] doctest in python and zope.testing have a bug, where do I report?

2009-08-11 Thread Gediminas Paulauskas
On Tue, Aug 11, 2009 at 3:57 PM, Chris Withersch...@simplistix.co.uk wrote:
 Chris Withers wrote:
 ValueError: Module-relative files may not have absolute paths

 Okay, so this is because the check is this little gem:

 if path.startswith('/'):
   raise ValueError, 'Module-relative files may not have absolute paths'

 Cross platform FAIL :-(

 A few questions:

 - how can this actually be written in a cross platform way? Absolute
 paths start with a drive letter on Windows, no?

os.path.isabs(path)

 - why are absolute paths bad here anyway? The code that causes this
 problem was:

     return DocFileSuite(
         optionflags=REPORT_NDIFF|ELLIPSIS,
         *glob(join(dirname(__file__),pardir,'docs','*.txt'))
         )

 I have a nagging feeling this has come up before, but still, the above
 seems to be viable if maybe not preferred?

Looks too complicated and yes that check looks redundant to me.


 - where do I report the cross platform bug? Python core tracker? What
 about zope.testing? Where does its tracker live now?

https://bugs.launchpad.net/zope.testing
___
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 )