Re: [Zope-dev] How to signal that projects have moved to github
On Thu, Jan 10, 2013 at 05:37:09PM -0500, Tres Seaver wrote: On 01/10/2013 03:16 PM, Marius Gedminas wrote: On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? +1 Feeling ambiguoous today, or maybe not? Eh. :-) An explicit +1 for svn rm .../trunk/*; svn add .../trunk/MOVED_TO_GITHUB.txt Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital 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] How to signal that projects have moved to github
On 10/01/2013 20:48, Jim Fulton wrote: It isn't just CI: people may have projects running from SVN checkouts, which we break without warning (the Plone devs have been notorious for causing such breakage for years). I still think breakage is better. If they're using trunk, without pinning a revision, it must be because they want the latest code. They won't get that from svn. This is a case where I think it's better to fail in an obvious way. Yeah, +1 from me here. If people think they're using trunk, and they're not 'cos its moved to GitHub, that's bad. FWIW, you may not know that GitHub really does have an svn interface to git repositories on GitHub. They unfortunately announced this on April 1 one year, so I think most people (myself included, until I actually started using it) assume it's a joke. So, it really is a case of CI tools changing their subversion url, and others doing a svn switch --relocate. cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ 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] Status of the buildout organization on github and a deleted branch
Hi, I thought I have was part of the buildout organization, but I am not now. I noticed because I wanted to recreate a branch that went missing. Could I either get commit access or could somebody recreate the 1.6.x branch. There is a buildout extension that breaks because of the missing branch. There seems to be no way to identify where exactly the branch was deleted, but the last mention of the branch is ef8c5e2a0d689e88e2a038f8346259e631956a1f Committed by Adam. I don't know if that was a merge that removed the branch or not, but as a starting point for a resurrected 1.6.x branch it seems bo ge good enough Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of the buildout organization on github and a deleted branch
The buildout 1.6.x branch was renamed to 1. Jim discussed and announced that on the buildout-development list. Please follow-up on that list for buildout issues. Hanno On Fri, Jan 11, 2013 at 1:51 PM, Patrick Gerken do3cc...@googlemail.comwrote: Hi, I thought I have was part of the buildout organization, but I am not now. I noticed because I wanted to recreate a branch that went missing. Could I either get commit access or could somebody recreate the 1.6.x branch. There is a buildout extension that breaks because of the missing branch. There seems to be no way to identify where exactly the branch was deleted, but the last mention of the branch is ef8c5e2a0d689e88e2a038f8346259e631956a1f Committed by Adam. I don't know if that was a merge that removed the branch or not, but as a starting point for a resurrected 1.6.x branch it seems bo ge good enough Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Changing id generation in OFS CopyContainer
I want to use INameChooser to select the id of copied content. This is currently not possible since manage_pasteObject does not pass the object to be pasted to _get_id. I added a new wichert-ofs-paste-naming branch to extend _get_id to make that possible. Are there any objections to merging that change to 2.13 and trunk? 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 )
[Zope-dev] Zope2 git mirror not updating?
I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? 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] Zope2 git mirror not updating?
On Jan 11, 2013, at 14:07 , Wichert Akkerman wich...@wiggy.net wrote: I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org. jens smime.p7s Description: S/MIME cryptographic 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] Zope2 git mirror not updating?
On Jan 11, 2013, at 14:10 , Jens Vagelpohl j...@dataflake.org wrote: On Jan 11, 2013, at 14:07 , Wichert Akkerman wich...@wiggy.net wrote: I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org. Ok, noted. Perhaps it would make sense to not give write access on github for repositories that are not officially migrated to prevent confusion? I'm afraid I committed something on both github and svn.zope.org now since I initially thought github was the thing to use. 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] Status of github migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 06:10 PM, Matthew Wilkes wrote: Tres Seaver wrote: What is needed is not scripts, but eyeballs: we need people who know the various packages and*care* about getting them migrated to github to step up. Softwward which doesn't have a champion willing to do the work should stay behind on SVN. The community as a whole cares about having them all migrated to github. I'm sure this will happen the next time there's a sprint, just like lots of them got migrated (and subsequently deleted) at the zope4 sprint in San Francisco a few years back. The communite as-a-whole demonstrably does *not* care about many of the projects on svn.zope.org. E.g.: https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html We need man-hours, sure, but not champions. Being blocked on working on the code because you're the first one to care about a package and subsequently have to learn how to do the migration is a crazy way of doing things. The foundation agreed to support moving projects to github, but that isn't a blank check. For instance, if there is substantial interest in having the projects pulled in by the current Plone buildout moved, make a list of them, and recruit the folks to step up and help with the migration for them. The effort requires includes doing the conversion, checking the results *by hand*, landing the repository, and fixing anything that breaks once you do (including stuff that breaks in projects you otherwise don't care about). Any project that can't find somebody willing to do that work (that is what I meant by a champion) is better off staying on SVN: we don't do ourselves favors by carrying all the unmaintained baggage of fifteen years worth of development forward, just for purity / completeness / whatever. 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/ iEYEARECAAYFAlDwMPQACgkQ+gerLs4ltQ6HowCgse8NF8ELeMXSLB4USzBJD1mE mRAAnRU1bygjDMqeb3rn/674V/FfuvZY =Erwd -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] Changing id generation in OFS CopyContainer
Hi. Sorry, but 2.13 is in bug-fix-only mode. At least as long as I have to do the release management for it. Trunk is fair game, or up to Leonardo really. Hanno On Fri, Jan 11, 2013 at 2:09 PM, Wichert Akkerman wich...@wiggy.net wrote: I want to use INameChooser to select the id of copied content. This is currently not possible since manage_pasteObject does not pass the object to be pasted to _get_id. I added a new wichert-ofs-paste-naming branch to extend _get_id to make that possible. Are there any objections to merging that change to 2.13 and trunk? 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 ) ___ 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] Status of github migration
On Fri, Jan 11, 2013 at 10:34 AM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 06:10 PM, Matthew Wilkes wrote: Tres Seaver wrote: What is needed is not scripts, but eyeballs: we need people who know the various packages and*care* about getting them migrated to github to step up. Softwward which doesn't have a champion willing to do the work should stay behind on SVN. The community as a whole cares about having them all migrated to github. I'm sure this will happen the next time there's a sprint, just like lots of them got migrated (and subsequently deleted) at the zope4 sprint in San Francisco a few years back. The communite as-a-whole demonstrably does *not* care about many of the projects on svn.zope.org. E.g.: https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html We need man-hours, sure, but not champions. Being blocked on working on the code because you're the first one to care about a package and subsequently have to learn how to do the migration is a crazy way of doing things. The foundation agreed to support moving projects to github, but that isn't a blank check. For instance, if there is substantial interest in having the projects pulled in by the current Plone buildout moved, make a list of them, and recruit the folks to step up and help with the migration for them. The effort requires includes doing the conversion, checking the results *by hand*, landing the repository, and fixing anything that breaks once you do (including stuff that breaks in projects you otherwise don't care about). Any project that can't find somebody willing to do that work (that is what I meant by a champion) is better off staying on SVN: we don't do ourselves favors by carrying all the unmaintained baggage of fifteen years worth of development forward, just for purity / completeness / whatever. +1 BTW (speaking of cruft), as someone who used/abused svn.zope.org as a generic open-source hosting service (when I should have used something like code.google.com, or bitbucket, or whatever), I wonder if there should be a process for petitioning to remove projects from the ZF repositories. (Maybe this only applies to me :) Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ 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] Building/Testing persistent package with tox
Hi guys, I have just tried to build/test persistent with tox and it fails with the following error message:: IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt' Complete output from command python setup.py egg_info: Traceback (most recent call last): File string, line 16, in module File /tmp/pip-u7jE1n-build/setup.py, line 29, in module open(os.path.join(here, 'CHANGES.txt')).read()) IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt This is indeed correct, since the ZIP package archive created by tox in ./.tox/dist does not include any txt files. I use the following command to run tox: $ tox -e py27,py32 How do others run tox? Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ 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] Building/Testing persistent package with tox
On Fri, Jan 11, 2013 at 10:54 AM, Stephan Richter stephan.rich...@gmail.com wrote: Hi guys, I have just tried to build/test persistent with tox and it fails with the following error message:: IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt' Complete output from command python setup.py egg_info: Traceback (most recent call last): File string, line 16, in module File /tmp/pip-u7jE1n-build/setup.py, line 29, in module open(os.path.join(here, 'CHANGES.txt')).read()) IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt This is indeed correct, since the ZIP package archive created by tox in ./.tox/dist does not include any txt files. I use the following command to run tox: $ tox -e py27,py32 How do others run tox? The project needs to be updated with a manifest that causes .txt files to be included in builds. (Look at zc.buildout for an example.) I planned to do this, but hadn't gotten to it yet. I can probably do that this weekend. This is needed because persistent has moved to git and setuptools/distribute, **thankfully**, don't support git without a plugin. **Please**, no one fix this by adding the plugin, at least not for any projects I'm heavily involved it. I far prefer the explicit approach afforded by a lack of VCS integration. IMO, avoiding the setuptools/distribute VCS magic is a major advantage of moving to git. :) Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ 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] Building/Testing persistent package with tox
On Friday, January 11, 2013 11:00:47 AM Jim Fulton wrote: The project needs to be updated with a manifest that causes .txt files to be included in builds. (Look at zc.buildout for an example.) I planned to do this, but hadn't gotten to it yet. I can probably do that this weekend. Okay, that makes sense. I was wondering about the manifest already, but I was not sure whether another mechanism was involved. BTW, the current bootstrap.py file does not work with Python 3. Are we not going to support buildout with Python 3 or what's the goal/story here? Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ 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] Becoming a zopefoundation member on GitHub
On Fri, Jan 11, 2013 at 10:55 AM, Stephan Richter stephan.rich...@gmail.com wrote: Hi everyone, what are the necessary steps to become a Zope Foundation organization member on GitHub? I would like to try moving a small product there to test the migration. You should have gotten an email from me a a few weeks ago requesting your github email. (It turns out I needed your id too.) Perhaps we didn't have an up-to-date email address for you in our database, or maybe it got files as spam. :) Please send me (privately) your github email and id. If any other contributors didn't get an email from me and want write access to the github repositories, please send me your github id and email. WRT moving or creating repositories, an unfortunate miss-feature of github is that developers with push access can't also create repositories. (This is one of the reasons that ZC uses bitbucket.) You'll have to ask someone (like me) to do that for you. I don't think we've formalized the process for this. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ 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] Building/Testing persistent package with tox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2013 10:54 AM, Stephan Richter wrote: Hi guys, I have just tried to build/test persistent with tox and it fails with the following error message:: IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt' Complete output from command python setup.py egg_info: Traceback (most recent call last): File string, line 16, in module File /tmp/pip-u7jE1n-build/setup.py, line 29, in module open(os.path.join(here, 'CHANGES.txt')).read()) IOError: [Errno 2] No such file or directory: '/tmp/pip-u7jE1n- build/CHANGES.txt This is indeed correct, since the ZIP package archive created by tox in ./.tox/dist does not include any txt files. I use the following command to run tox: $ tox -e py27,py32 How do others run tox? Nice catch: this is a side-effect of the move to Git. I just run 'tox' (all environments), but the Python's I use for tox all have setuptools_git installed, so the CHANGES.txt gets included in the temporary sdist. I guess we can ass a MANIFEST.in, since you are certainly not going to be the last person to trip over this issue. /me tries using a Python without setuptools_git: Hmm, the zipefile is built correctly for me. Odd. The two tarballs are identical. 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/ iEYEARECAAYFAlDwOuoACgkQ+gerLs4ltQ7DsACeLIUyz6XocYMSAvdpuY6f9JOe k/4AoJBw/sQA/fLyXVoJZotawPh7I4fg =x2TZ -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] Building/Testing persistent package with tox
On Fri, Jan 11, 2013 at 11:05 AM, Stephan Richter stephan.rich...@gmail.com wrote: ... BTW, the current bootstrap.py file does not work with Python 3. Are we not going to support buildout with Python 3 or what's the goal/story here? Buildout 2, which is still in alpha, but all I use works with Python 3. Use: http://downloads.buildout.org/2/bootstrap.py and don't forget to use -t, since buildout 2 isn't final. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ 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] Becoming a zopefoundation member on GitHub
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2013 11:11 AM, Jim Fulton wrote: WRT moving or creating repositories, an unfortunate miss-feature of github is that developers with push access can't also create repositories. (This is one of the reasons that ZC uses bitbucket.) You'll have to ask someone (like me) to do that for you. I don't think we've formalized the process for this. The Foundation's repository committee is Jens plus the folks who have been helping him maintain SVN (Andreas, Jim, ~me). At this point, that group is effectively the only set which can create repositories on Github (the Owners group). Tell one of that group that you want to migrate a project: they will create a new, empty repository for you and grant access. 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/ iEYEARECAAYFAlDwPY8ACgkQ+gerLs4ltQ6A2wCdGSNdH1DGILvPwTPZEAAAxGFJ utUAoJx86L35qyb6TTZTT2oMNZopDadq =xGJH -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 25, OK: 17
This is the summary for test reports received on the zope-tests list between 2013-01-10 00:00:00 UTC and 2013-01-11 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 Fixed - zopetoolkit_trunk - Build # 137 Fixed - zopetoolkit_trunk_app - Build # 120 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [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 [5]winbot / z3c.configurator_py_265_32 [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.ptcompat_py_265_32 [8]winbot / z3c.recipe.paster_py_265_32 [9]winbot / z3c.sampledata_py_265_32 [10] winbot / zc.sourcefactory_py_265_32 [11] winbot / zope.app.applicationcontrol_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.component_py_265_32 [15] winbot / zope.app.container_py_265_32 [16] winbot / zope.app.exception_py_265_32 [17] winbot / zope.app.generations_py_265_32 [18] winbot / zope.app.publisher_py_265_32 [19] winbot / zope.app.publisher_py_265_32 [20] winbot / zope.app.rotterdam_py_265_32 [21] winbot / zope.app.security_py_265_32 [22] winbot / zope.app.session_py_265_32 [23] winbot / zope.app.session_py_265_32 [24] winbot / zope.app.testing_py_265_32 [25] winbot / zope.app.zcmlfiles_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 / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071327.html [2]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071328.html [3]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071329.html [4]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071330.html [5]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071307.html [6]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071332.html [7]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071304.html [8]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071333.html [9]FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071334.html [10] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071306.html [11] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071305.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071340.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071301.html [14] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071309.html [15] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071338.html [16] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071337.html [17] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071302.html [18] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071331.html [19] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071299.html [20] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071308.html [21] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071303.html [22] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071339.html [23]
