Re: [Zope-dev] procedures for moving package to github and porting to Python 3

2013-03-04 Thread Jan-Wijbrand Kolman
On 3/1/13 5:29 PM, Stephan Richter wrote: On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: megrok.menu It's done now, but it lost its 0.1 tag due to a conversion issue. Great! And thanks again! regards, jw ___ Zope-Dev

Re: [Zope-dev] zope-tests - FAILED: 18, OK: 13

2013-03-04 Thread Marius Gedminas
On Mon, Mar 04, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Repository policy check found errors in 436 projects Contains a broken link to http://uter.gocept.com/~ctheune/report-2013-03-03T02:15:02.792640.txt (Host uter.gocept.com not found: 3(NXDOMAIN)) I suspect the script

[Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-04 Thread Andrey Lebedev
Hello zope-dev, As you may already know, there is an effort to port zope packages to Python 3 going on. As part of this effort we want to port zope.testbrowser. Unfortunately, mechanize package, that zope.testbrowser depends on has no py3 support. There is an unfinished effort at [1],

[Zope-dev] GitHub and Travis CI

2013-03-04 Thread Stephan Richter
Hi everyone, I have invested some time today to implement the Travis CI hook setup for GitHub. I can now turn on and update Travis CI for any package. Right now, there is no reporting setup. But Travis CI can be configured to send out E-mails and give IRC notifications. In addition, Marius

Re: [Zope-dev] GitHub and Travis CI

2013-03-04 Thread Hanno Schlichting
On Mon, Mar 4, 2013 at 8:00 PM, Stephan Richter stephan.rich...@gmail.com wrote: So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. Cool, but please change the default email notification, it's set to spam everyone all the time. See

Re: [Zope-dev] ZTK 2.0: Deprecate zope.sequencesort

2013-03-04 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2013 10:34 PM, Arfrever Frehtes Taifersar Arahesis wrote: 2013-02-28 21:04:33 Tres Seaver napisa?(a): I have ported it to Python 3.2 and 3.3 and released a 4.0.0 version. There are still multiple problems (types.TupleType,

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

2013-03-04 Thread Zope tests summarizer
This is the summary for test reports received on the zope-tests list between 2013-03-03 00:00:00 UTC and 2013-03-04 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:

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

2013-03-04 Thread Marius Gedminas
On Tue, Mar 05, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 191 Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg [2]winbot / z3c.contents_py_265_32 [3]winbot /

Re: [Zope-dev] GitHub and Travis CI

2013-03-04 Thread Adam GROSZER
On 03/04/2013 08:00 PM, Stephan Richter wrote: So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. And probably include the status in the usual daily zope-test email. Tho no idea where that script is running and where the source is. --

[Zope-dev] Who has the winbot/rackspace creds?

2013-03-04 Thread Adam GROSZER
Hello, It would be time to do a backup/snapshot of the VM. -- Best regards, Adam GROSZER -- Quote of the day: The man who smiles when things go wrong has thought of someone he can blame it on. - Jones' Law ___ Zope-Dev maillist -