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.
Hi,
I wanted to fix some logging in Products.SiteErrorLog, but I am confused
where to go to.
zopefoundation on github has a small number of repos but not
Products.SiteErrorLog.
http://svn.zope.org shows me a web view of our old cvs server.
There is something wrong. Can I help with something?
Best regards,
Patrick
This is the summary for test reports received on the
zope-tests list between 2013-01-29 00:00:00 UTC and 2013-01-30 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 # 156
Successful - zopetoolkit_trunk_app - Build # 139
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
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
[1] winbot / z3c.recipe.paster_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 / z3c.recipe.paster_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-January/071787.html
I wanted to have an up-to-date status page for the status of the Python
3 porting efforts of various zope-ish packages, so I made one:
http://zope3.pov.lt/py3/
Source for the data extraction bits: https://github.com/mgedmin/ztk-py3-status
Source for the presentation bits: use View Source in your browser.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
This is the summary for test reports received on the
zope-tests list between 2013-01-28 00:00:00 UTC and 2013-01-29 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 # 155
Successful - zopetoolkit_trunk_app - Build # 138
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
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
[1] winbot / ZODB_dev py_270_win64
[2] winbot / z3c.recipe.paster_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_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-January/071764.html
[2] FAILED winbot / z3c.recipe.paster_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-January/071765.html
This is the summary for test reports received on the
zope-tests list between 2013-01-27 00:00:00 UTC and 2013-01-28 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 # 154
Successful - zopetoolkit_trunk_app - Build # 137
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
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
[1] winbot / z3c.recipe.paster_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 / z3c.recipe.paster_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-January/071743.html
This is the summary for test reports received on the
zope-tests list between 2013-01-26 00:00:00 UTC and 2013-01-27 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 # 153
Successful - zopetoolkit_trunk_app - Build # 136
Total languishing bugs for zope2: 0
[1] Total languishing bugs for zope: 64
[2] Total languishing bugs for zopeapp: 1
[3] Total languishing bugs for zopetoolkit: 205
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
winbot / ZODB_dev py_265_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
[4] winbot / z3c.recipe.paster_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 Total languishing bugs for zope: 64
https://mail.zope.org/pipermail/zope-tests/2013-January/071720.html
[2] FAILED Total languishing bugs for zopeapp: 1
https://mail.zope.org/pipermail/zope-tests/2013-January/071718.html
[3] FAILED Total languishing bugs for zopetoolkit: 205
https://mail.zope.org/pipermail/zope-tests/2013-January/071719.html
[4] FAILED winbot / z3c.recipe.paster_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-January/071717.html
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/27/2013 11:55 AM, David Glick (Plone) wrote:
> On 1/27/13 6:00 PM, Tres Seaver wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 01/27/2013 08:49 AM, Julien Cristau wrote:
>>> On Mon, Nov 26, 2012 at 18:53:58 +0900, Arnaud Fontaine wrote:
>>>
>>>> Tres Seaver <tseaver(a)palladion.com> writes:
>>>>
>>>>>> * CVE-2012-5505 (zope.traversing: atat.py)
>>>>>> http://plone.org/products/plone/security/advisories/20121106/21
>>>>>
>>>>>>
That "fix" is also disputed: hiding the "default" view from the
>>>>> '@@' name does not actually improve security at all. There
>>>>> is a Launchpad bug where it is being debated (#1079225), but
>>>>> that bug is still in "Private Security" mode. The correct
>>>>> fix is to change the code of the multi-adapter to barf if
>>>>> published via a URL.
>>>> Any idea when this patch will be released? Thanks.
>>>>
>>> Is there any news on that issue?
>> I still believe the report is in error: we cannot hide default
>> (unnamed) views simply because an application might register one in
>> error. Any views which wants not to be called via URLs needs to
>> handle that directly: registering a multiadapter for (IThing, None)
>> *is* registering a view.
>>
>>
> Plone includes the configuration of zope.annotation which registers a
> multiadapter of (IAnnotations, Interface) that, as far as I can tell,
> is not intended as a view and can expose information that was meant to
> be private. Our patch therefore monkey-patched the view traverser in
> zope.traversing to prevent it from being published. zope.annotation is
> not configured in Zope 2 out of the box.
If you believe that the '(IAnnotation, None)' registration is not
supposed to be a view, then the correct place to address this is in
'zope.annotation', not the publisher. E.g.:, the attached patch.
Note that the two-argument registration was added by Jacob Holm in r72995
(2007-03-05). CC'ing him to ask if he can recall the justification, or
knows what would break if we removed it. At a guess, the motivator is
zope.app.preference, which wnats the extra argument passed to its
__new__: this is *not* a reason to reguster a multi-adapter.
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)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlEFbAEACgkQ+gerLs4ltQ6vSgCff1kX2u+mhrvly+m0uBSg5DD+
nBoAoMVdVCnKzrHwPIleuHhHIHpM7Xkw
=e1VT
-----END PGP SIGNATURE-----