[Zope-dev] z3c.schema
Hi,
I added nl translations to z3c.schema, could someone grant me
('janjaapdriessen') pypi access so I can release this as 0.7.1?
Thanks,
--
Jan-Jaap Driessen
___
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] z3c.schema
Am 31.03.2011 um 08:23 schrieb Jan-Jaap Driessen:
Hi,
I added nl translations to z3c.schema, could someone grant me
('janjaapdriessen') pypi access so I can release this as 0.7.1?
Hi,
you now have the Owner role in the project.
Yours sincerely,
--
Michael Howitz · m...@gocept.com · software developer
gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1
Zope and Plone consulting and development
___
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] z3c.schema
On 3/31/11 08:23 , Jan-Jaap Driessen wrote:
Hi,
I added nl translations to z3c.schema, could someone grant me
('janjaapdriessen') pypi access so I can release this as 0.7.1?
Can you reply to my comment on your translation commit? I don't think
the current language used in z3c.schema is very user friendly.
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] z3c.schema
On 31 March 2011 08:42, Wichert Akkerman wich...@wiggy.net wrote:
On 3/31/11 08:23 , Jan-Jaap Driessen wrote:
Hi,
I added nl translations to z3c.schema, could someone grant me
('janjaapdriessen') pypi access so I can release this as 0.7.1?
Can you reply to my comment on your translation commit? I don't think the
current language used in z3c.schema is very user friendly.
Wichert.
Per Wichert's suggestion I have removed the RFC822 mention from the
user-facing error messages in r121172.
I had to add these dependencies in order to get `i18nextract` to work,
could anybody with more i18n skills have a look?
http://svn.zope.org/z3c.schema/trunk/buildout.cfg?rev=121172r1=92501r2=121172
I'll wait with a release until this is fixed.
Thanks,
--
Jan-Jaap Driessen
___
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: 109 OK, 24 Failed, 4 Unknown
2011/3/25 Gediminas Paulauskas mene...@pov.lt: Buildout tries to download ClientForm from sourceforge.net and seems to get a broken content-length header. I see the same problem when using distutils 0.6.14 since the last 3 or 4 days. But when I use wget the header seems to be correct or wget is smart enough to fix it. ClientForm 0.2.10 (and mechanize 0.1.11) downloads do not exhibit this problem. I have updated zope.release to these versions to make buildbot green. No, this did not help to fix the 3.4 KGS, newer versions also failed to download. ___ 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: 109 OK, 24 Failed, 4 Unknown
2011/3/23 Laurence Rowe l...@lrowe.co.uk: On 23 March 2011 14:43, Tres Seaver tsea...@palladion.com wrote: Multiple 'Content-Length' headers is definitely a Bad Thing. I filed a bug, which Mark Ramm has promised to escalate: https://sourceforge.net/apps/trac/sourceforge/ticket/18486 I have a patch for setuptools which works around it: http://bugs.python.org/setuptools/issue123 I'm not sure how to work around the issue at the moment. I always add the following to my buildout.cfg to avoid problems with random third party servers: allow-hosts = *.python.org *.plone.org launchpad.net (launchpad.net is there only for mocker which does not have a pypi release). I have added the following sites to allow-hosts for SchoolTool, that needs Sphinx, Pygments, PIL, reportlab, pyPdf, Paste. allow-hosts = buildout.org code.google.com effbot.org *.googlecode.com pybrary.net pygments.org *.python.org pythonpaste.org *.pythonware.com *.pocoo.org reportlab.com *.repoze.org *.schooltool.org Not all sites are needed, but why block projects official downloads? Gediminas ___ 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] [Distutils] [buildout] private releases
On Wed, Mar 30, 2011 at 15:08, Jim Fulton j...@zope.com wrote: We do something similar with sftp (zc.buildoutsftp). To publish eggs, we just use scp. The advantage of this is that it leverages ssh infrastructure, so *no* additional password management is needed. This is wildly better, IMO, than keeping passwords in clear text in your buildout configuration or in a dot file. That depends on your deployment scenarios. We generate separate passwords per customer, and give them a dedicated URL to load their private eggs from, then put the password in the buildout.cfg. To load the buildout.cfg in the first place, the exact same password is used. Managing SSH accounts and keys for those customers would cost us much more overhead, and would complicate our instructions for deployment to them. On the other hand, for deployments of a buildout from a SVN repository already served over SSH would make the sftp route the logical choice. -- Martijn Pieters ___ 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: 78 OK, 10 Failed
Summary of messages to the zope-tests list. Period Wed Mar 30 11:00:00 2011 UTC to Thu Mar 31 11:00:00 2011 UTC. There were 88 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 23 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036655.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036656.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036657.html Subject: FAILED : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036658.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036659.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:01:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/03.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:27:07 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036668.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 22:32:38 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036674.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 22:43:08 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036675.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 23:17:23 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036676.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:47:44 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036599.html Subject: OK : Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:49:11 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036600.html Subject: OK : Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:50:38 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036601.html Subject: OK : Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:52:02 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036602.html Subject: OK : Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:53:23 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036603.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 08:59:55 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036604.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:05:54 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036605.html Subject: OK : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:10:35 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036606.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:11:42 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036607.html Subject: OK : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:13:16 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036608.html Subject: OK : Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:16:29 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036609.html Subject: OK : Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:21:20 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036610.html Subject: OK : Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Mar 30 09:26:04 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036611.html Subject:
Re: [Zope-dev] [Distutils] [buildout] private releases
On Thu, Mar 31, 2011 at 5:38 AM, Martijn Pieters m...@zopatista.com wrote: On Wed, Mar 30, 2011 at 15:08, Jim Fulton j...@zope.com wrote: We do something similar with sftp (zc.buildoutsftp). To publish eggs, we just use scp. The advantage of this is that it leverages ssh infrastructure, so *no* additional password management is needed. This is wildly better, IMO, than keeping passwords in clear text in your buildout configuration or in a dot file. That depends on your deployment scenarios. We generate separate passwords per customer, and give them a dedicated URL to load their private eggs from, then put the password in the buildout.cfg. To load the buildout.cfg in the first place, the exact same password is used. Managing SSH accounts and keys for those customers would cost us much more overhead, and would complicate our instructions for deployment to them. On the other hand, for deployments of a buildout from a SVN repository already served over SSH would make the sftp route the logical choice. Some customers are too dumb to be secure. OK, makes sense. :) Seriously, I assume this is a read-only scenario, in which case having clear-text passwords laying around in prominent places seems less problematic. If they could write to the repo, then I would still have serious problems with this approach. Another approach would be to integrate with some secure key-management service (keychain) on the customer's machines, but I expect that would be as painful as helping them figure out ssh. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ 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: 109 OK, 24 Failed, 4 Unknown
On 31 March 2011 10:15, Gediminas Paulauskas mene...@pov.lt wrote: 2011/3/23 Laurence Rowe l...@lrowe.co.uk: On 23 March 2011 14:43, Tres Seaver tsea...@palladion.com wrote: Multiple 'Content-Length' headers is definitely a Bad Thing. I filed a bug, which Mark Ramm has promised to escalate: https://sourceforge.net/apps/trac/sourceforge/ticket/18486 I have a patch for setuptools which works around it: http://bugs.python.org/setuptools/issue123 I'm not sure how to work around the issue at the moment. I always add the following to my buildout.cfg to avoid problems with random third party servers: allow-hosts = *.python.org *.plone.org launchpad.net (launchpad.net is there only for mocker which does not have a pypi release). I have added the following sites to allow-hosts for SchoolTool, that needs Sphinx, Pygments, PIL, reportlab, pyPdf, Paste. allow-hosts = buildout.org code.google.com effbot.org *.googlecode.com pybrary.net pygments.org *.python.org pythonpaste.org *.pythonware.com *.pocoo.org reportlab.com *.repoze.org *.schooltool.org Not all sites are needed, but why block projects official downloads? Limiting your allowed hosts to the minimal set makes running buildout much faster as most of the network requests get blocked. Laurence ___ 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: 78 OK, 10 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2011 06:57 AM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Wed Mar 30 11:00:00 2011 UTC to Thu Mar 31 11:00:00 2011 UTC. There were 88 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 23 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036655.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036656.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036657.html Subject: FAILED : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036658.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036659.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:01:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/03.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:27:07 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036668.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 22:32:38 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036674.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 22:43:08 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036675.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 23:17:23 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036676.html Woohoo! the ZTK and Zope2 buildbots are green! Now if we can just get the rest there. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UdQkACgkQ+gerLs4ltQ7ZmwCgsJ1Yha6GI8gE2Tp6BW8YdPMT //AAoJnJcR518Ec0BJvHsjw3KUlyAAUN =LNUV -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: 74 OK, 19 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/30/2011 07:43 PM, Marius Gedminas wrote: On Wed, Mar 30, 2011 at 12:57:54PM +0200, Zope Tests Summarizer wrote: Test failures - Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Tue Mar 29 21:01:43 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036574.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Tue Mar 29 21:27:19 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036575.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Tue Mar 29 22:29:28 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036581.html So, it's been a week, and the SourceForge bug [1] is still not fixed. [1] http://sourceforge.net/apps/trac/sourceforge/ticket/18486 There are three other possible workarounds: 1. Put ClientForm and mechanize into the buildout cache on the build slave, so buildout doesn't try to go look for newer versions elsewhere. This ought to work: one of the four builders is still green, for this reason. 2. Add an allow-hosts option to buildout.cfg -- except it's generated by a tool I'm not familiar with (zope.kgs.buildout). Maybe I could tweak ~/.pydistutils.cfg on the buildslave? 3. Update versions.cfg in the KGS 3.4 to require a newer setuptools version or distribute, then release it as KGS 3.4.2a1. Except the only setuptools version with the fix is a prerelease (0.6c12dev-r88975). I don't like (1) and (2) because they're local fixes: any user trying to actually use the 3.4 KGS will trip on this problem. In that sense it's useful to have these buildbots red: we know the problem is not fixed yet for the users (assuming the 3.4 KGS still has any). I don't like (3) because, ick, pinning a svn snapshot version? Not cool. It looks like the 'generate-buildout' script from zope.kgs uses a static 'buildout.cfg.in' template. The following patch should do to add 'allow-hosts':: - -- % -- - --- src/zope/kgs/buildout.cfg.in (revision 121173) +++ src/zope/kgs/buildout.cfg.in(working copy) @@ -1,6 +1,9 @@ [buildout] parts = test versions = versions +allow-hosts = +pypi.python.org +*.zope.org [test] recipe = zc.recipe.testrunner - -- % -- Stephan, does that look OK to you? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UdqIACgkQ+gerLs4ltQ54UgCgn0JBa3b68wnDV0HDb8wOBiuU ldAAn1XC/7bqa21sg3urR2tRSh0q2jun =vaQl -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 )
