Re: [Zope-dev] zope-tests - FAILED: 86, OK: 5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGsjhoACgkQ+gerLs4ltQ4+SACglPxJ5J5b7eJV5yUfADFVjeAR bJsAoNJYhnaciMoGMqkP14KRGsFiO7ux =qGub -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 86, OK: 5
On Jun 3, 2013, at 14:37 , Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: It also doesn't help that buildout 2 switched to requiring distribute just before distributed was merged into setuptools again. Wichert. ___ 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: 86, OK: 5
On 06/03/2013 02:37 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads I think it's the first. It seems to be a distribute vs setuptools fight. I recently installed distribute in site-packages, but that does not seem to help. -- Best regards, Adam GROSZER -- Quote of the day: A man without God is not like a cake without raisins; he is like a cake without the flour and milk; he lacks the essential ingredients... - Bishop Fulton J. Sheen ___ 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: 86, OK: 5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2013 09:04 AM, Adam GROSZER wrote: On 06/03/2013 02:37 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/02/2013 09:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-06-01 00:00:00 UTC and 2013-06-02 00:00:00 UTC: I'm not sure where we are with these failures. I can't reproduce the exact failures on fresh checkouts, but I believe we are in a weird state due to a combination of factors: - - distribute / setuptools merger - - PyPI now HTTPS-only - - PyPI CDN caching? I think we should be aiming to switch our bootstraps over ASAP to pick up setuptools 0.7: it doesn't appear to be simple at the moment to get that installed, as there is no 'ez_setup.py' in the beta location: https://bitbucket.org/pypa/setuptools/downloads I think it's the first. It seems to be a distribute vs setuptools fight. I recently installed distribute in site-packages, but that does not seem to help. Would it help to update to setuptools-0.7 in the 'site-packages' (removing distribute completely)? I have the feeling that the faster we put setuptools-0.6 and distribute behind us, the better off we will be. I've played with it some this morning: the major issue for our buildouts is to get an 'ez_setup.py' selected which doesn't look for setuptools-0.7 on PyPI -- I don't quite know why, but it is only available here: https://bitbucket.org/pypa/setuptools/downloads The attached file woks for me using e.g.: $ /path/to/python bootstrap.py --setup-source=file:///tmp/ez_setup.py Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGsr2oACgkQ+gerLs4ltQ4fcwCcCKice5D4MObbCuUEkeq88AT3 F+UAoI5Jlfwa44MsmfpPOO4Z1i9kVfO0 =Iiof -END PGP SIGNATURE- ez_setup.py Description: application/httpd-cgi ___ 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-tests - FAILED: 78, OK: 5
This is the summary for test reports received on the zope-tests list between 2013-06-02 00:00:00 UTC and 2013-06-03 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 Successful - zopetoolkit_trunk - Build # 285 [1]winbot / BTrees_py_265_32 [2]winbot / ZODB_dev py_265_win32 [3]winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [4]winbot / ZODB_dev py_270_win64 [5]winbot / persistent_py_265_32 [6]winbot / transaction_py_265_32 [7]winbot / z3c.baseregistry_py_265_32 [8]winbot / z3c.batching_py_265_32 [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.language.negotiator_py_265_32 [12] winbot / z3c.language.session_py_265_32 [13] winbot / z3c.pdftemplate_py_265_32 [14] winbot / z3c.recipe.paster_py_265_32 [15] winbot / z3c.viewtemplate_py_265_32 [16] winbot / z3c.xmlhttp_py_265_32 [17] winbot / z3c.zrtresource_py_265_32 [18] winbot / zc.catalog_py_265_32 [19] winbot / zc.configuration_py_265_32 [20] winbot / zc.i18n_py_265_32 [21] winbot / zc.monitor_py_265_32 [22] winbot / zc.ngi_py_265_32 [23] winbot / zc.resourcelibrary_py_265_32 [24] winbot / zc.table_py_265_32 [25] winbot / zope.annotation_py_265_32 [26] winbot / zope.app.applicationcontrol_py_265_32 [27] winbot / zope.app.appsetup_py_265_32 [28] winbot / zope.app.basicskin_py_265_32 [29] winbot / zope.app.broken_py_265_32 [30] winbot / zope.app.component_py_265_32 [31] winbot / zope.app.container_py_265_32 [32] winbot / zope.app.content_py_265_32 [33] winbot / zope.app.debug_py_265_32 [34] winbot / zope.app.error_py_265_32 [35] winbot / zope.app.exception_py_265_32 [36] winbot / zope.app.folder_py_265_32 [37] winbot / zope.app.form_py_265_32 [38] winbot / zope.app.generations_py_265_32 [39] winbot / zope.app.i18n_py_265_32 [40] winbot / zope.app.interface_py_265_32 [41] winbot / zope.app.localpermission_py_265_32 [42] winbot / zope.app.pagetemplate_py_265_32 [43] winbot / zope.app.principalannotation_py_265_32 [44] winbot / zope.app.rotterdam_py_265_32 [45] winbot / zope.app.schema_py_265_32 [46] winbot / zope.app.security_py_265_32 [47] winbot / zope.app.security_py_265_32 [48] winbot / zope.app.server_py_265_32 [49] winbot / zope.app.session_py_265_32 [50] winbot / zope.app.testing_py_265_32 [51] winbot / zope.app.wsgi_py_265_32 [52] winbot / zope.app.zcmlfiles_py_265_32 [53] winbot / zope.app.zopeappgenerations_py_265_32 [54] winbot / zope.browser_py_265_32 [55] winbot / zope.cachedescriptors_py_265_32 [56] winbot / zope.cachedescriptors_py_265_32 [57] winbot / zope.configuration_py_265_32 [58] winbot / zope.contenttype_py_265_32 [59] winbot / zope.copy_py_265_32 [60] winbot / zope.deprecation_py_265_32 [61] winbot / zope.dottedname_py_265_32 [62] winbot / zope.event_py_265_32 [63] winbot / zope.filerepresentation_py_265_32 [64] winbot / zope.hookable_py_265_32 [65] winbot / zope.i18nmessageid_py_265_32 [66] winbot / zope.interface_py_265_32 [67] winbot / zope.lifecycleevent_py_265_32 [68] winbot / zope.proxy_py_265_32 [69] winbot / zope.schema_py_265_32 [70] winbot / zope.server_py_265_32 [71] winbot / zope.size_py_265_32 [72] winbot / zope.testbrowser_py_265_32 [73] winbot / zope.testing_py_265_32 winbot / ztk_10 py_254_win32 [74] winbot / ztk_10 py_265_win32 [75] winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 [76] winbot / ztk_11 py_265_win32 [77] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [78] winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075733.html [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-June/075705.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075706.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-June/075708.html [5]FAILED winbot / persistent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075755.html [6]FAILED winbot / transaction_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075712.html [7]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075724.html [8]FAILED winbot / z3c.batching_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075774.html [9]FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-June/075745.html [10] FAILED winbot /
[Zope-dev] RFC: branch updating zc.buildout and bootstraps to use setuptools 0.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The bloody state of the winbot at the moment seems tied to issues related to setuptools 0.6, distribute 0.5.4x, and zc.buildout. I put in some effort today on a branch to end-run the whole old-setuptools / distribute bit by updating buildout2 to use the newly-availabe (but not yet released to PyPI) setuptools 0.7. This version is the first release after the merge of old setuptools and distribute, and should be the preferred target for future work. My branch of buildout is here: https://github.com/tseaver/buildout/tree/use-setuptools-0.7 with a pull request to the main repo: https://github.com/buildout/buildout/pull/123 One issue that has to be worked around in the near term: the 0.7 release has been published via the bitbucket downloads page: but not pushed to the cheeseshop. I uploaded a hacked version of 'ez_setup.py' to deal with that interim problem here: http://dist.repoze.org/ez_setup-0.7.py and my buildout branch uses that version. I would like some help getting the manuel + renormalizer + doctest tests working, or at least getting the spurious output differences smoothed away so we can see real semantic changes, if any. I'm assuming that it will take some days (weeks?) to get them passing, by which point we can hope that the 0.7 release has been pushed to PyPI (relieveing the need for a double-secret version of 'ez_setup.py'). Thoughts? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGtQgUACgkQ+gerLs4ltQ59zwCeOScg3hciUGN3IyAltHfM0+eS x/QAoMlUvQ5ifgiWnhuyQXqqdcP3Jjag =BbxG -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope] Pword reset tools
It looks like there are no pa55word reset products for straight Zope that are still maintained i.e. a feature to allow users to reset their own pa55words via email linking into aclusers. If that is correct does anybody have any pointers for implementing such a mechanism with a one time email reset tool? TIA (Re-posted to remove administrivia keywords!) ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-CMF] cmf-tests -
This is the summary for test reports received on the cmf-tests list between 2013-06-02 00:00:00 UTC and 2013-06-03 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 Non-OK results -- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
