- Zope-Dev - Zope lists

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1312 Blamelist: andreasjung BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1311 Blamelist: andreasjung BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1308 Blamelist: philikon BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1307 Blamelist: jinty,philikon BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

ZSQL method and LIMIT clause
by Thanh Hải, Hà 03 Nov '05

03 Nov '05

Hello, My problem is I don't know to prevent Zope from adding "LIMIT 1000" to the end of each of my ZSQL method (*.zsql). I am developing a filesystem-based product so I can not disable it by setting "Maximum Rows to Retrieve" to zero in the ZMI interface. I got stuck with this problem for a couple of weeks (google search and read documentation didn't help). Any help is greatly appreciated.

3 3

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1305 Blamelist: yuppie BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 03 Nov '05

03 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1304 Blamelist: rogerineichen,srichter,tlotze,yuppie BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

PAS tests failures
by Julien Anguenot 03 Nov '05

03 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I got tests failing with the following configuration : FC4 Zope-2.8.4 Python 2.3.5 / 2.4.2 PAS trunk as below : ====================================================================== FAIL: Doctest: ChallengeProtocolChooser.txt - ---------------------------------------------------------------------- Traceback (most recent call last): File "/opt/Zope-2.8.4/lib/python/zope/testing/doctest.py", line 2102, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for ChallengeProtocolChooser.txt File "/home/zopes/zope2.8.4/Products/PluggableAuthService/plugins/tests/ChallengeProtocolChooser.txt", line 0 and all the failures within this doctest look like this one : - ---------------------------------------------------------------------- File "/home/zopes/zope2.8.4/Products/PluggableAuthService/plugins/tests/ChallengeProtocolChooser.txt", line 260, in ChallengeProtocolChooser.txt Failed example: print http(r""" POST /%s HTTP/1.1 Content-Type: text/xml; charset="utf-8" <?xml version="1.0"?> <methodCall> <methodName>test_script</methodName> </methodCall> """ % (folder_name), handle_errors=False) Exception raised: Traceback (most recent call last): File "/opt/Zope-2.8.4/lib/python/zope/testing/doctest.py", line 1315, in __run compileflags, 1) in test.globs File "<doctest ChallengeProtocolChooser.txt[62]>", line 1, in ? print http(r""" File "/opt/Zope-2.8.4/lib/python/Testing/ZopeTestCase/zopedoctest/functional.py", line 180, in http debug=not handle_errors, File "/opt/Zope-2.8.4/lib/python/ZPublisher/Test.py", line 193, in publish_module response = publish(request, module_name, after_list, debug=debug) File "/opt/Zope-2.8.4/lib/python/ZPublisher/Publish.py", line 144, in publish sys.exc_info()[2], File "/opt/Zope-2.8.4/lib/python/ZPublisher/Publish.py", line 104, in publish object=request.traverse(path, validated_hook=validated_hook) File "/opt/Zope-2.8.4/lib/python/ZPublisher/BaseRequest.py", line 461, in traverse response.unauthorized() File "/opt/Zope-2.8.4/lib/python/ZPublisher/HTTPResponse.py", line 684, in unauthorized raise Unauthorized, m Unauthorized: <strong>You are not authorized to access this resource.</strong> With Zope-2.7.8 the tests pass just fine. Any idea about the problem ? J. - -- Julien Anguenot | Nuxeo R&D (Paris, France) CPS Platform : http://www.cps-project.org Zope3 / ECM : http://www.z3lab.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDaXQHGhoG8MxZ/pIRAkYLAJ4upanns7PRDyYHNgSxHXkJk476IACdFfMy U6mOq7W8VdrXr0EEcCENIoU= =JMU+ -----END PGP SIGNATURE-----

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 02 Nov '05

02 Nov '05

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1295 Blamelist: chrism,efge,fdrake,jim,philikon,srichter BUILD FAILED: failed compile sincerely, -The Buildbot

1 0

Maintenance cycles for Zope 2.X branches
by Andreas Jung 02 Nov '05

02 Nov '05

Hi, because of the fact that we are switching to a time-based release cycle for Zope 2 and Zope 3. I would like to discuss how deal with the maintenance of older branches. My idea is to support branches for one year from now on. Zope 2.7 should be maintained until the end of this year, Zope 2.8 until the release of Zope 2.10 in June 2006, Zope 2.9 until the release of Zope 2.11 in December 2006. In case of severe bugs and security problems we can think of making releases for deprecated Zope versions. We could extend the maintenance period for releases if there are some volunteers to take over the responsibility for older branches (isn't there a maintainer for the Linux 2.0 kernel? :-)) From the maintenance point of view it just a nightmare (and it takes a lot of time) to have an overview over more than two or three branches. What do you think? Andreas

3 2