On Fri, Feb 15, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:

[1] FAILED Still Failing - zopetoolkit_trunk - Build # 172 https://mail.zope.org/pipermail/zope-tests/2013-February/072294.html

Ignored, because Build # 173 is right there.

[2] FAILED Still Failing - zopetoolkit_trunk - Build # 173 https://mail.zope.org/pipermail/zope-tests/2013-February/072304.html

Error: Picked: zope.container = 3.12.0 Oh, look, Build # 174 also exists (and is also failing). Error: Picked: BTrees = 4.0.5 Okay. Here's what's happening: * Latest ZODB3 was split into independent ZODB, ZEO, BTrees, persistent, transaction packages (the latter two were split out earlier). * Bleeding edge zope.container started depending on these smaller packages instead of depending on the monolithic ZODB3. * zopetoolkit points to ZODB3/branches/3.10, i.e. before the split * I suspect that trying to develop = ZODB3 version 3.10.x and BTrees is not going to work well, since both will be trying to put 'BTrees' onto your sys.path What does the zope toolkit want to do with this? Pin zope.container to an earlier branch, maybe?

[3] FAILED Still Failing - zopetoolkit_trunk_app - Build # 155 https://mail.zope.org/pipermail/zope-tests/2013-February/072295.html

Build # 156 is latest and it fails with the same issue.

[4] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072293.html

Haven't looked at it yet.

[5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072333.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[6] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072322.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[7] FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072323.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[8] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072320.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[9] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072353.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072331.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[11] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072332.html

[12] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072351.html

[13] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072343.html

[14] FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072337.html

[15] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072339.html

[16] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072335.html

[17] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072326.html

[18] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072319.html

[19] FAILED winbot / z3c.template_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072324.html

[20] FAILED winbot / z3c.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072321.html

[21] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072329.html

[22] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072350.html

[23] FAILED winbot / z3c.zrtresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072346.html

I didn't even look. I expect they all depend on the same thing which depends on zope.security[untrustedpython]. It's annoying that buildout (or easy_install) doesn't tell you what package is declaring a dependency on the unknown extra.

[24] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072338.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[25] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072341.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[26] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072349.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[27] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072327.html

[28] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072325.html

[29] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072336.html

[30] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072352.html

[31] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072344.html

[32] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072348.html

Didn't look, assume the same.

[33] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072330.html

Looked. UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[34] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072340.html

[35] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072334.html

[36] FAILED winbot / zope.browsermenu_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072342.html

[37] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072328.html

[38] FAILED winbot / zope.mimetype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072318.html

[39] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072347.html

Didn't look.

[40] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072345.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython'

[41] FAILED winbot / zope.viewlet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072317.html

UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' Okay. Here's what's happening: * zope.security is an important package that blocks Python 3 work of many other packages. * zope.security[untrustedpython] used to depend on RestrictedPython, which is hard to port to Python 3. * zope.security[untrustedpython] was extracted into a separate zope.untrustedpython package so it wouldn't block zope.security's port. * Tres finished the zope.security port and pushed a 4.0.0a1 release (yay!). * All packages that used to depend on zope.security[untrustedpython] are now broken. I suggest we add an untrustedpython extra to zope.security that depends on zope.untrustedpython. And a zope.security.untrustedpython package that emits a deprecation warning on import time and does from zope.untrustedpython import *. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development