May 2015 - Zope-Dev - Zope lists

zope-tests - OK: 13
by Zope tests summarizer 22 May '15

22 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-21 00:00:00 UTC and 2015-05-22 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 # 1019 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - OK: 13
by Zope tests summarizer 21 May '15

21 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-20 00:00:00 UTC and 2015-05-21 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 # 1018 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - OK: 13
by Zope tests summarizer 20 May '15

20 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-19 00:00:00 UTC and 2015-05-20 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 # 1017 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

1 0

zope-tests - FAILED: 4, OK: 9
by Zope tests summarizer 20 May '15

20 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-15 00:00:00 UTC and 2015-05-16 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 # 1013 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088317.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088318.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088319.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088320.html

3 4

zope-tests - FAILED: 4, OK: 9
by Zope tests summarizer 19 May '15

19 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-18 00:00:00 UTC and 2015-05-19 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 # 1016 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088797.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088798.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088799.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088800.html

1 0

zope-tests - FAILED: 4, OK: 9
by Zope tests summarizer 18 May '15

18 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-17 00:00:00 UTC and 2015-05-18 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 # 1015 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088637.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088638.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088639.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088640.html

1 0

zope-tests - FAILED: 4, OK: 9
by Zope tests summarizer 17 May '15

17 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-16 00:00:00 UTC and 2015-05-17 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 # 1014 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088477.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088478.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2015-May/088479.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2015-May/088480.html

1 0

Re: [Zope-dev] A Tale of Two Repositories
by Tres Seaver 16 May '15

16 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/15/2015 07:07 AM, Maurits van Rees wrote: > Tres Seaver schreef op 14-05-15 om 21:14: >> Contributor Workflow: Github ----------------------------- >> >> Github-based contributors will follow normal Github workflow >> patterns: >> >> - Fork the repository of interest via the Github UI. > > If they have contributor acccess to the original repository, they can > of course create a branch in this original github repository. I class "contributor" as distinct from "maintainer", based on exactly those rights, although we might want to adopt a pattern where even maintainers function as though they were contributors, submitting pull requests for review by another maintainer. > I was going to say: "the same is true for Launchpad," but on Launchpad > we should of course not do any manual changes to the original > repository, because it is meant to be only touched by the automatic > synchronisation. I don't have enough Git-fu to work out how to automate two-way synchronization, which is why I described having the LP repository be a read-only mirror. >> The Launchpad repository will be synched automatically, whether by >> the cron job or by the built-in Launchpad mirroring. > > Does anyone know if we can make the Launchpad repository read-only > except for the synchronization? This would prevent accidental > commits. Well, I guess the access rights can be tweaked. If the repo > can only be written to by one Zope Foundation or CMF account, this > would prevent accidental commits by individual contributors. If Launchpad supports it, then having the commit rights restricted to the mirroring process would be great. > Sounds good to me. > Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJVV7x5AAoJEPKpaDSJE9HYz6YQAIFqpC3pHG8lr1RE3N3DNtw/ Ijyo9tlRhIlKWIX4HGcOk9IqW3+E95Y4jZlgbYIREONc0+GDJAMZcT0qhEZrcihD 93aT55dutC3SqFx/QHqQoPLI8jjumYjnXxbUxPwajSfTR8Hffi62LsGmQjjCk6cK bM3N7HjCaYiFNy/sAV0hIFCbS8Ps1s1EzdcQF8HJV/ls2B2X26CQR9zoe4OQBSJB Zb/KrTHr0HY/FVMRyV4JNw6oMgbDtQ5sEzmQ6drUtsKIHyBfK2qMqwlIgqc4e4KS RsXg34ZxEA5ll+wmW0iqF7LE+IIbtNI5NVXo3IZU+aZtRKAWYpxQ8AzsyD5G/mzA OEVKXuWn7n7u6qwzcRYrHtyUk1VmxrBNN86zpeRU2bJYSK03Pp55XKfiq/OeeHn2 vQBlXfpng4yw9PkCgoSYLtpXKvfcRQZ30IC8eeQcLuO78xYZSWapT7rg1cXFcd9H 0Ug5pxWkarRSZZMrsivoQTcbvRK3nFsgMPi787BSknk6L6DzXJNysRO/Tghd5HGP D4Sx5iRVYVbw07IHsv/7QsVDWtuL8RvoSddalOy3fuMiDYWUrPQDK4t1KF4Uf5q4 DKVT65+00tYYmnBnFXSeUHHHFSWshf61fsUFcFqvRnYDhltZKBCNMg6Kruj+eHG+ 6xW3qWt+x8g+KEPRkk6i =RY1y -----END PGP SIGNATURE-----

1 0

Re: [Zope-dev] A Tale of Two Repositories
by yuppie 16 May '15

16 May '15

Hi Tres, Tres Seaver wrote: > The CMF projects are in this state because one of the main developers is > unwilling to participate in the project if it moves entirely to > Github[2], but is willing to continue if a proposal is in place to > maintain a second public repository, against which his contributions > would be made[3]. This proposal aims to satisfy that request by hosting > the second, synchronized repository for each project using the new > Launchpad Git hosting option[4]. thanks for working on this issue. I'm not very happy about the proposed solution because it makes the GitHub repository the primary repository and the canonical location for bug reports. But compromises never make everybody happy. I'm happy about your proposal because it looks like a practicable solution everybody can live with. > 1) Create a Git repository from its Subversion history, and push that > repository to Github; this step will use the same scripts used for > other ZF repositories. E.g., the branches, tags, and trunk for > ``Products.CMFCore`` will be hosted on Github at > https://github.com/zopefoundation/Products.CMFCore There is one problem with the existing procedure: author information is lost for contributers without GitHub account. I don't know if this is a bug in the scripts or if the GitHub universe is a closed universe that has no provisions for handling information about people existing outside. Would be nice if this could be resolved. I consider it an unfriendly act to remove my name from all my contributions just because I'm no customer of GitHub Inc. And it makes history information less useful. Please note https://github.com/zopefoundation/Products.GenericSetup already exists, but is not in sync with the version in the Subversion repository. And please don't forget the dev buildouts in http://svn.zope.org/CMF/. Cheers, Yuppie

3 2

zope-tests - FAILED: 25, OK: 13
by Zope tests summarizer 15 May '15

15 May '15

This is the summary for test reports received on the zope-tests list between 2015-05-14 00:00:00 UTC and 2015-05-15 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 # 1012 [1] winbot / BTrees_py_265_32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.form_py_265_32 [3] winbot / z3c.xmlhttp_py_265_32 [4] winbot / zc.ngi_py_265_32 [5] winbot / zc.table_py_265_32 [6] winbot / zope.app.applicationcontrol_py_265_32 [7] winbot / zope.app.appsetup_py_265_32 [8] winbot / zope.app.localpermission_py_265_32 [9] winbot / zope.app.principalannotation_py_265_32 [10] winbot / zope.app.publisher_py_265_32 [11] winbot / zope.app.schema_py_265_32 [12] winbot / zope.app.zopeappgenerations_py_265_32 [13] winbot / zope.cachedescriptors_py_265_32 [14] winbot / zope.componentvocabulary_py_265_32 [15] winbot / zope.configuration_py_265_32 [16] winbot / zope.copypastemove_py_265_32 [17] winbot / zope.exceptions_py_265_32 [18] winbot / zope.index_py_265_32 [19] winbot / zope.keyreference_py_265_32 [20] winbot / zope.password_py_265_32 [21] winbot / zope.principalannotation_py_265_32 [22] winbot / zope.principalregistry_py_265_32 [23] winbot / zope.publisher_py_265_32 [24] winbot / zope.tal_py_265_32 [25] winbot / zope.testbrowser_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088289.html [2] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088287.html [3] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088271.html [4] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088270.html [5] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088274.html [6] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088288.html [7] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088280.html [8] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088277.html [9] FAILED winbot / zope.app.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088275.html [10] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088283.html [11] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088293.html [12] FAILED winbot / zope.app.zopeappgenerations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088282.html [13] FAILED winbot / zope.cachedescriptors_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088294.html [14] FAILED winbot / zope.componentvocabulary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088278.html [15] FAILED winbot / zope.configuration_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088286.html [16] FAILED winbot / zope.copypastemove_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088273.html [17] FAILED winbot / zope.exceptions_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088291.html [18] FAILED winbot / zope.index_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088272.html [19] FAILED winbot / zope.keyreference_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088285.html [20] FAILED winbot / zope.password_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088279.html [21] FAILED winbot / zope.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088276.html [22] FAILED winbot / zope.principalregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088292.html [23] FAILED winbot / zope.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088284.html [24] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088281.html [25] FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2015-May/088290.html

1 0