[Zope-dev] Repository cleanup: ZVSL licensed files?
Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev 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] Repository cleanup: ZVSL licensed files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2tPCgACgkQRAx5nvEhZLL8YgCgus5vn8TGP8NG4of72QgNd3w2 mrUAnjlhNmoWrGhGVTC14GVffvoVt53p =R0Sq -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] Repository cleanup: ZVSL licensed files?
On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. Sorry our (probably my) bad. Those should have been fixed when we moved them from our repo to the zope.org repo. Does the patch fix the files? Or just list them? 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] Repository cleanup: ZVSL licensed files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 15:19 , Jim Fulton wrote: On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. Sorry our (probably my) bad. Those should have been fixed when we moved them from our repo to the zope.org repo. Does the patch fix the files? Or just list them? Hi Jim, It just lists them as part of the weekly repository policy check that flows into the automated test summary email. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2tjN0ACgkQRAx5nvEhZLJmKACfY6GV0XHrlNFvalMlE5qHB7uq MkwAoISBeGWkwOHW4K9CqZDM4tIy5vD0 =yFXe -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] Repository cleanup: ZVSL licensed files?
Am 19.04.2011 um 15:19 schrieb Jim Fulton: On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. Sorry our (probably my) bad. Those should have been fixed when we moved them from our repo to the zope.org repo. Does the patch fix the files? Or just list them? Currently it only lists them. I think there are not so many packages, so it might be easier to fix them manually. 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] Repository cleanup: ZVSL licensed files?
On Tue, Apr 19, 2011 at 9:23 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 15:19 , Jim Fulton wrote: On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. Sorry our (probably my) bad. Those should have been fixed when we moved them from our repo to the zope.org repo. Does the patch fix the files? Or just list them? Hi Jim, It just lists them as part of the weekly repository policy check that flows into the automated test summary email. OK. I normally don't read that mail. I'll check in a week or so and if I see the list, I'll clean them up. 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] [Zope2] Multiline response headers causing problems for proxies.
On 18 April 2011 17:01, Laurence Rowe l...@lrowe.co.uk wrote: When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both Varnish [1] and Nginx [2] which may then mangle the header value. In fact the HTTP 1.0 spec notes that splitting over multiple lines in not recommended [3], though the HTTP 1.1 spec does not mention this explicitly, though it does say [4]: Applications ought to follow common form, where one is known or indicated, when generating HTTP constructs, since there might exist some implementations that fail to accept anything Are there any objections to me applying the attached patch to Zope 2.13 and trunk? Laurence [1] http://www.varnish-cache.org/trac/ticket/905 [2] http://nginx.org/pipermail/nginx-devel/2011-April/000859.html [3] http://tools.ietf.org/html/rfc1945#section-4.2 [4] http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html I've now applied this to 2.13 and trunk. If it causes any problems, let me know. 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 )
[Zope-dev] zope-tests - FAILED: 9, OK: 76, UNKNOWN: 1
This is the summary for test reports received on the zope-tests list between 2011-04-18 00:00:00 UTC and 2011-04-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 [1]UNKNOWN : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.5 : Linux Zope-2.12-alltests Python-2.6.5 : Linux Zope-2.13 Python-2.6.5 : Linux Zope-2.13-alltests Python-2.6.5 : Linux Zope-trunk Python-2.6.5 : Linux Zope-trunk-alltests Python-2.6.5 : Linux winbot / ZODB_dev py_254_win32 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.coverage_py_265_32 [3]winbot / z3c.rml_py_265_32 [4]winbot / z3c.rml_py_265_32 [5]winbot / z3c.rml_py_265_32 [6]winbot / zc_buildout_dev py_254_win32 [7]winbot / zc_buildout_dev py_265_win32 [8]winbot / zc_buildout_dev py_265_win64 [9]winbot / zc_buildout_dev py_270_win32 [10] winbot / zc_buildout_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_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 https://mail.zope.org/pipermail/zope-tests/2011-April/038523.html [2]FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038496.html [3]FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038521.html [4]FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038494.html [5]FAILED winbot
