I'm forwarding this from the CMF list as I'm stumped. I worked my way up
the debug stack but couldn't find what was causing one Zope instance to
decode to unicode and the other to leave content as utf-8 (or maybe it's
the other way round?). Both instances on the same machine.
Any ideas?
This is the summary for test reports received on the
zope-tests list between 2012-11-28 00:00:00 UTC and 2012-11-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:
On 11/29/2012 08:20 PM, Charlie Clark wrote:
I'm forwarding this from the CMF list as I'm stumped. I worked my way up
the debug stack but couldn't find what was causing one Zope instance to
decode to unicode and the other to leave content as utf-8 (or maybe it's
the other way round?). Both
Hi, just sending again to the list...
On Tuesday 27 Nov 2012 16:51:13 Andreas Jung wrote:
Use the right tool for each problem. Zope is really not the right choice
for implementing a websocket server.
Why is it the wrong tool for the job? I read up a bit on asyncore, and see
it's supposedly a
This is the summary for test reports received on the
zope-tests list between 2012-11-27 00:00:00 UTC and 2012-11-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:
Hi,
* Alex Leach albl...@york.ac.uk [2012-11-25 20:00]:
I was wondering if anyone has implemented a WebSockets server API using the
zope toolkit? I've just submitted a blueprint on Launchpad
(https://blueprints.launchpad.net/zopetoolkit-project/+spec/websockets-api),
but thought it might
On 11/27/2012 09:04 AM, Wolfgang Schnerring wrote:
Hi,
* Alex Leach albl...@york.ac.uk [2012-11-25 20:00]:
I was wondering if anyone has implemented a WebSockets server API using the
zope toolkit? I've just submitted a blueprint on Launchpad
Hi,
Thanks for the reply.
On Tuesday 27 Nov 2012 09:04:11 Wolfgang Schnerring wrote:
I'm not too familiar with WebSocket internals, but one thing that stuck
with me is that you'll need to keep *lots* of open connections, which is
only feasible with an eventloop-based server (which
On Tuesday 27 Nov 2012 10:07:03 Adam GROSZER wrote:
Some investigations and trials showed about half a year ago that a
Autobahn + Twisted + pyramid combination worked.
YMMV
Thanks. That is a completely different and separate application stack cf. the
standard grok dependencies. I've
On Tue, Nov 27, 2012 at 3:04 AM, Wolfgang Schnerring w...@gocept.com wrote:
...
I'm not too familiar with WebSocket internals, but one thing that stuck
with me is that you'll need to keep *lots* of open connections, which is
only feasible with an eventloop-based server (which zope.server, for
On Tuesday 27 Nov 2012 07:04:43 Jim Fulton wrote:
Actually, it is. zope.server is based on asyncore.
Having said that, my impression is that web sockets is largely (or
completely) orthogonal to WSGI and the HTTP-based publishing
infrastructure.
From the RFC:
The WebSocket Protocol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Leach wrote:
It is a bag of useful libraries :) Is there anything that would ease
the development of a WebSockets server, though? I would have thought
there is, and that it would be at least possible, if not simple, to
implement from
This is the summary for test reports received on the
zope-tests list between 2012-11-26 00:00:00 UTC and 2012-11-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:
Hello,
Tres Seaver tsea...@palladion.com writes:
version 2.12.21: * LP #1079238 fixes CVE 2012-5489.
According to the upstream changelog, LP #1047318 seems to fix a
security bug, but I could not find it in zope2 launchpad nor anywhere
else.
That bug was still in Private Security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2012 08:00 PM, Zope tests summarizer wrote:
[6]UNKNOWN UNKNOWN : Zope-2.13 Python-2.7.3 : Linux
https://mail.zope.org/pipermail/zope-tests/2012-November/069550.html
[7]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.8 : Linux
This is the summary for test reports received on the
zope-tests list between 2012-11-25 00:00:00 UTC and 2012-11-26 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:
Hi,
I was wondering if anyone has implemented a WebSockets server API using the
zope toolkit? I've just submitted a blueprint on Launchpad
(https://blueprints.launchpad.net/zopetoolkit-project/+spec/websockets-api),
but thought it might be quicker and easier to discuss how one could do this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2012 09:07 PM, Arnaud Fontaine wrote:
Luciano Bello luci...@debian.org writes:
Hi, please see : http://seclists.org/oss-sec/2012/q4/249
Can you confirm if any of the Debian packages are affected?
As far as I could find (not clear
This is the summary for test reports received on the
zope-tests list between 2012-11-24 00:00:00 UTC and 2012-11-25 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-23 00:00:00 UTC and 2012-11-24 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:
Hello,
Luciano Bello luci...@debian.org writes:
Hi, please see : http://seclists.org/oss-sec/2012/q4/249
Can you confirm if any of the Debian packages are affected?
As far as I could find (not clear in the upstream changelog):
version 2.12.26:
* LP #1071067 fixes CVE 2012-5507, CVE
This is the summary for test reports received on the
zope-tests list between 2012-11-22 00:00:00 UTC and 2012-11-23 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-21 00:00:00 UTC and 2012-11-22 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/22/2012 08:00 PM, Zope tests summarizer wrote:
[1]UNKNOWN UNKNOWN : Zope-2.13 Python-2.7.3 : Linux
https://mail.zope.org/pipermail/zope-tests/2012-November/069479.html
Failure in boostrap::
Running /usr/local/python2.7/bin/python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
Why was the 'layer' ZCML argument removed in zope.component 4.0?
Until now, I didn't recognize that it was long deprecated.
Here ist the CHANGES.txt entry from pypi:
http://pypi.python.org/pypi/zope.component
Removed the long-deprecated layer
Hi,
does the current version of
Products.ZCTextIndex.ZCTextIndex.ZCTextIndex.index_object method
seems ok about keeping optimization?
If so, what is the process to release a new version because we
really need this in our projects and in
On Wed, Nov 21, 2012 at 2:00 AM, Zope tests summarizer nore...@zope.orgwrote:
This is the summary for test reports received on the
zope-tests list between 2012-11-19 00:00:00 UTC and 2012-11-20 00:00:00
UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of
On Wed, Nov 21, 2012 at 8:56 AM, Patrick Gerken do3cc...@googlemail.com wrote:
On Wed, Nov 21, 2012 at 2:00 AM, Zope tests summarizer nore...@zope.org
wrote:
This is the summary for test reports received on the
zope-tests list between 2012-11-19 00:00:00 UTC and 2012-11-20 00:00:00
UTC:
This is the summary for test reports received on the
zope-tests list between 2012-11-20 00:00:00 UTC and 2012-11-21 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-19 00:00:00 UTC and 2012-11-20 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-18 00:00:00 UTC and 2012-11-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:
This is the summary for test reports received on the
zope-tests list between 2012-11-17 00:00:00 UTC and 2012-11-18 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-16 00:00:00 UTC and 2012-11-17 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-15 00:00:00 UTC and 2012-11-16 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/16/2012 08:00 PM, Zope tests summarizer wrote:
[1]UNKNOWN UNKNOWN : Zope-2.13 Python-2.7.3 : Linux
https://mail.zope.org/pipermail/zope-tests/2012-November/069344.html
[2]UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux
This is the summary for test reports received on the
zope-tests list between 2012-11-14 00:00:00 UTC and 2012-11-15 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:
Hello Johannes,
On Sat, 2012-11-10 at 20:54 +0100, johannes raggam wrote:
If you have some comments and suggestions regarding zope.org, drop me
a mail.
The pages from top-level navigation links such as sitemap,
accessibility-info, contact-info and site search toolbar's text are not
in English.
Hi everybody,
I made a small change in the current Products.ZCTextIndex product,
the change can be saw here :
http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/ZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689
and I added a test here
Hi.
The change looks ok. But I think you broke an optimization. IIRC the code
compares the old and new values for the index, and skips the indexing step
if they are the same. The typical item.reindexObject() call sents data for
all indexes, even if just one or two them have changed. The
Am 14.11.2012, 16:26 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
Hi.
The change looks ok. But I think you broke an optimization. IIRC the code
compares the old and new values for the index, and skips the indexing
step
if they are the same. The typical item.reindexObject() call sents
Hi Hanno,
I did not know if checking the current index value could be faster
or slower than indexing anyway.
I think that checking the current index length could do what we
need :
Keeping the current code and changing this :
This is the summary for test reports received on the
zope-tests list between 2012-11-13 00:00:00 UTC and 2012-11-14 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-12 00:00:00 UTC and 2012-11-13 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-11 00:00:00 UTC and 2012-11-12 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-10 00:00:00 UTC and 2012-11-11 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:
On Mon, Nov 12, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2012-11-10 00:00:00 UTC and 2012-11-11 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,,,
with the help of Jens Vagelpohl i upgraded zope.org to the newest
Plone 4.2.2 patched with the Plone Hotfix 20121106 security update
released this week. http://www.zope.org/
I also restructured the World of Zope section for better relevance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2012 02:54 PM, johannes raggam wrote:
Hello,,,
with the help of Jens Vagelpohl i upgraded zope.org to the newest
Plone 4.2.2 patched with the Plone Hotfix 20121106 security update
released this week. http://www.zope.org/
I also
This is the summary for test reports received on the
zope-tests list between 2012-11-09 00:00:00 UTC and 2012-11-10 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-08 00:00:00 UTC and 2012-11-09 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2012 08:27 AM, Sylvain Viollon wrote:
Op 7 nov 2012, om 14:21 heeft Sylvain Viollon het volgende
geschreven:
Op 6 nov 2012, om 20:17 heeft Leonardo Rochael Almeida het volgende
geschreven:
Hi Silvain,
Thanks for the deep
This is the summary for test reports received on the
zope-tests list between 2012-11-07 00:00:00 UTC and 2012-11-08 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:
Op 6 nov 2012, om 20:17 heeft Leonardo Rochael Almeida het volgende geschreven:
Hi Silvain,
Thanks for the deep analysis. Did you put this code in a branch
somewhere for us to take a look?
I created a branch here:
http://svn.zope.org/AccessControl/branches/sylvain-memory-leak/
Op 7 nov 2012, om 14:21 heeft Sylvain Viollon het volgende geschreven:
Op 6 nov 2012, om 20:17 heeft Leonardo Rochael Almeida het volgende
geschreven:
Hi Silvain,
Thanks for the deep analysis. Did you put this code in a branch
somewhere for us to take a look?
I created a branch
This is the summary for test reports received on the
zope-tests list between 2012-11-06 00:00:00 UTC and 2012-11-07 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:
Hello,
I recently find out I had a memory leak in Silva, with Python 2.7. After
playing a while with various tools (objgraph is nice), I found out I leaked
between two and three objects at every request:
- an AccessControl.SecurityManagement.SecurityContext instance,
- two bound
Hi Silvain,
Thanks for the deep analysis. Did you put this code in a branch
somewhere for us to take a look?
Cheers,
Leo
On Tue, Nov 6, 2012 at 2:54 PM, Sylvain Viollon sylv...@infrae.com wrote:
Hello,
I recently find out I had a memory leak in Silva, with Python 2.7. After
playing a
This is the summary for test reports received on the
zope-tests list between 2012-11-05 00:00:00 UTC and 2012-11-06 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-04 00:00:00 UTC and 2012-11-05 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-03 00:00:00 UTC and 2012-11-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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/04/2012 08:00 PM, Zope tests summarizer wrote:
[6]FAILED winbot / z3c.form_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-November/069103.html
This test failure is due to your change in r128159 (adding the prefix
string to
This is the summary for test reports received on the
zope-tests list between 2012-11-02 00:00:00 UTC and 2012-11-03 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:
This is the summary for test reports received on the
zope-tests list between 2012-11-01 00:00:00 UTC and 2012-11-02 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-31 00:00:00 UTC and 2012-11-01 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:
On Wed, Oct 31, 2012 at 01:00:02AM +, Zope tests summarizer wrote:
Non-OK results
--
[1]FAILED winbot / z3c.form_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-October/068988.html
Looks like fallout from
This is the summary for test reports received on the
zope-tests list between 2012-10-30 00:00:00 UTC and 2012-10-31 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:
Martin Aspeli optilude+li...@gmail.com writes:
On 7 June 2012 07:20, Michael Howitz m...@gocept.com wrote:
Am 06.06.2012 um 19:58 schrieb Hanno Schlichting:
[…]
As I said above, my main concern is keeping publisher events and
exception views intact. Some of these events need to happen in
This is the summary for test reports received on the
zope-tests list between 2012-10-29 00:00:00 UTC and 2012-10-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:
Hi,
I have migrated zope from Cent OS 5 to 6. Now I am getting the following
error when I try to save or run external method using mysql:
*Error Type: ImportError*
*Error Value: libmysqlclient_r.so.15: cannot open shared object file: No
such file or directory*
*
*
Any help to fix this is highly
Hi,
This is the mailing list to discuss development of Zope itself. It's
not strictly a support mailing list. You should likely contact:
https://mail.zope.org/mailman/listinfo/zope
In any case, by googling [libmysqlclient_r.so.15 centos 6]
I found this page:
On Mon, Oct 29, 2012 at 2:00 AM, Zope tests summarizer nore...@zope.org wrote:
Reports received
...
Total languishing bugs for zope2: 0
HORRAY,
zope2 is bugfree now!
___
Zope-Dev maillist - Zope-Dev@zope.org
This is the summary for test reports received on the
zope-tests list between 2012-10-28 00:00:00 UTC and 2012-10-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:
This is the summary for test reports received on the
zope-tests list between 2012-10-27 00:00:00 UTC and 2012-10-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:
This is the summary for test reports received on the
zope-tests list between 2012-10-26 00:00:00 UTC and 2012-10-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:
This is the summary for test reports received on the
zope-tests list between 2012-10-25 00:00:00 UTC and 2012-10-26 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-24 00:00:00 UTC and 2012-10-25 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:
On Tue, Oct 23, 2012 at 3:00 AM, Zope tests summarizer nore...@zope.org wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 51
[2]Still Failing - zopetoolkit_trunk_app - Build # 35
These bots have been fixed and don't fail any longer.
___
This is the summary for test reports received on the
zope-tests list between 2012-10-22 00:00:00 UTC and 2012-10-23 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:
Hi all
I have sent an email to zodb-dev about this but I thought I'd see if people
here could shed some light on the issue as well. This time I will state the
issue form a more Zope-client perspective.
Basically after an arbitrary amount of time I start getting these errors in
the Zope client
On Mon, Oct 22, 2012 at 5:12 AM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/2012 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Failure - zopetoolkit_trunk - Build # 50
This is the summary for test reports received on the
zope-tests list between 2012-10-21 00:00:00 UTC and 2012-10-22 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-20 00:00:00 UTC and 2012-10-21 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/2012 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Failure - zopetoolkit_trunk - Build # 50
https://mail.zope.org/pipermail/zope-tests/2012-October/068769.html
[2]FAILED Failure - zopetoolkit_trunk_app - Build # 34
This is the summary for test reports received on the
zope-tests list between 2012-10-19 00:00:00 UTC and 2012-10-20 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-18 00:00:00 UTC and 2012-10-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:
This is the summary for test reports received on the
zope-tests list between 2012-10-17 00:00:00 UTC and 2012-10-18 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-16 00:00:00 UTC and 2012-10-17 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:
Le 09/10/12 09:39, Jens Vagelpohl a écrit :
Hi all,
During the discussion about new ways to host and manage code in Zope Foundation
repositories one omission we had never really addressed became clear: What is
the status of patches reaching us by people who have not signed the contributor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/2012 09:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / ztk_11 py_270_win32
https://mail.zope.org/pipermail/zope-tests/2012-October/068654.html
Race conditions in zope.testrunner doctests (on order in which LAYER
FINISHED is
This is the summary for test reports received on the
zope-tests list between 2012-10-15 00:00:00 UTC and 2012-10-16 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:
On Mon, Oct 15, 2012 at 01:00:02AM +, Zope tests summarizer wrote:
[6]FAILED winbot / ztk_10 py_254_win32
https://mail.zope.org/pipermail/zope-tests/2012-October/068627.html
The bootstrap step failed with
error: Download error for
AFAIK this is still open, moved to Zope-Dev.
On Sun, Apr 24, 2011 at 12:18 PM, Martin Aspeli optil...@gmx.net wrote:
Hi,
On 23 April 2011 19:10, David Glick dgl...@gmail.com wrote:
On 4/21/11 9:57 AM, Laurence Rowe wrote:
On 21 April 2011 10:19, Roel Brugginkr...@fourdigits.nl wrote:
Hi,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2012 09:00 PM, Zope tests summarizer wrote:
[6]FAILED winbot / ztk_10 py_254_win32
https://mail.zope.org/pipermail/zope-tests/2012-October/068627.html
Should be a transient failure:
error: Download error for
This is the summary for test reports received on the
zope-tests list between 2012-10-14 00:00:00 UTC and 2012-10-15 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-13 00:00:00 UTC and 2012-10-14 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-12 00:00:00 UTC and 2012-10-13 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-11 00:00:00 UTC and 2012-10-12 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:
This is the summary for test reports received on the
zope-tests list between 2012-10-10 00:00:00 UTC and 2012-10-11 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2012 09:00 PM, Zope tests summarizer wrote:
[1]UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux
https://mail.zope.org/pipermail/zope-tests/2012-October/068558.html
Transient(?) failure:
While:
Installing test.
Getting
In 2008, the `zope_i18n_allowed_languages` environment setting was
introduced to limit the languages for which a message catalog is
loaded when you register translations using the registerTranslation
ZCML directive, and to be able to negotiate a list from a list of
available languages.
This
901 - 1000 of 34194 matches
Mail list logo
