-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/10/11 22:31 , Chris Withers wrote:
Hi All,
I found a link off the new site (which looks great, btw) to:
http://zodb.zope.org/
...but this name doesn't resolve for me, does it for other people?
The link is incorrect. It should point to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/11/11 02:04 , Alex Clark wrote:
Hi,
On 5/10/11 5:38 AM, Lennart Regebro wrote:
On Tue, May 10, 2011 at 09:15, Jens Vagelpohlj...@dataflake.org wrote:
I strongly disagree on the term Zope 2. Now is a great time to finally
stop the Zope2/3
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 09:09 , Suresh V. wrote:
Please see:
http://stackoverflow.com/questions/5603459/genericsetup-what-does-toolset-xml-accomplish-if-toolinit-still-has-to-be-called
I could not create a cmf tag, so if you can please add that to the
tags
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 11:18 , Lennart Regebro wrote:
On Sat, Apr 9, 2011 at 10:11, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 09:09 , Suresh V. wrote:
Please see:
http://stackoverflow.com/questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/3/11 12:41 , Jens Vagelpohl wrote:
On 3/29/11 11:15 , Adam GROSZER wrote:
But it seems like it's about bugging Stephan Holek to stop the current
one and bugging Jens to start the new one, or? Unless the script is broken.
Could you run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/4/11 08:37 , Jens Vagelpohl wrote:
On 4/3/11 12:41 , Jens Vagelpohl wrote:
On 3/29/11 11:15 , Adam GROSZER wrote:
But it seems like it's about bugging Stephan Holek to stop the current
one and bugging Jens to start the new one, or? Unless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/29/11 11:15 , Adam GROSZER wrote:
But it seems like it's about bugging Stephan Holek to stop the current
one and bugging Jens to start the new one, or? Unless the script is broken.
Could you run that script -- worst case we'll have 2 mails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/2/11 12:15 , Suresh V. wrote:
How come the following versions are not found in svn tags?
Products.CMFCore: Versions 2.2.1, 2.2.2, 2.2.3
I have no idea where you are looking, but those tags exist. See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/8/11 12:11 , Marco Bizzarri wrote:
I'd like to force Zope to reload the cache; of course, I could access
various pages using a wget or something liket that; but how can I force Zope
to 'fill' all connections, and just one?
Fire off several
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/7/11 22:28 , William Heymann wrote:
I have a monkey patch here that I would like comments on it and to see how it
works for others.
Hi William,
A huge monkey patch like that makes it very hard to compare it with the
original implementation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/1/10 08:59 , Wichert Akkerman wrote:
On 2010-12-1 07:43, Christian Theune wrote:
Here's the draft we ended up with yesterday:
http://dpaste.com/281566/
Can you move the non-OK results above the list of reports received? That
way you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/1/10 09:28 , Wichert Akkerman wrote:
On 12/1/10 09:04 , Jens Vagelpohl wrote:
On 12/1/10 08:59 , Wichert Akkerman wrote:
On 2010-12-1 07:43, Christian Theune wrote:
Here's the draft we ended up with yesterday:
http://dpaste.com/281566/
Can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/30/10 16:06 , Christian Theune wrote:
Hi,
here's a shot at a new format of the aggregated mails.
My focus on this draft was:
- allow dealing with *lots* of results every day more easily
- allow having a graphical overview of how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/1/10 07:43 , Christian Theune wrote:
On 11/30/2010 06:04 PM, Jens Vagelpohl wrote:
Looks good to me, much better than what we have now. I'm guessing the
URLs will be fixed to point to http://mail.zope.org... instead of
file:///tmp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/10 12:29 , Hanno Schlichting wrote:
- zopectl start - doen't work (https://bugs.launchpad.net/zope2/+bug/628448)
- Zope2 egg is not available in index
(https://bugs.launchpad.net/zope2/+bug/653546)
Both of these have been resolved now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/10 13:58 , CMF Tests Summarizer wrote:
Summary of messages to the cmf-tests list.
Period Wed Oct 20 12:00:00 2010 UTC to Thu Oct 21 12:00:00 2010 UTC.
There were 4 messages: 4 from CMF Tests.
Unknown
---
Subject: UNKNOWN :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/10 20:45 , Charlie Clark wrote:
Am 23.09.2010, 12:47 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Let's talk about 2.2 releases after the bug day then.
Hi Jens,
I'd like a 2.2 release to include the fixes to
CMFDefault/browser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/10 16:04 , Sascha Welter wrote:
The problem is solved though, thanks to Jens having called the hosting
company. I had contacted him and two other people directly, because I
soon noticed that this list was offline too, due to running on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/6/10 18:33 , Tres Seaver wrote:
+1 for dropping the test: if we aren't going to try to fix it to pass,
then scrap it. Note that I actually feel the same way about *all* the
every-day failures: the value of the every-day mail drops sharply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/30/10 21:16 , Marius Gedminas wrote:
On Thu, Sep 30, 2010 at 03:04:09PM +0200, Jens Vagelpohl wrote:
On 9/30/10 14:37 , Marius Gedminas wrote:
Can someone with admin access add a daily cron script to
cd /path/to/ztk/doc/sources
touch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/1/10 10:22 , Charlie Clark wrote:
Hi,
I'll admit to spending most of my time on new CMF stuff but I did close
two bugs that I felt comfortable with. Didn't seem anyone else was hanging
around on IRC with bugfixing on their mind.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/30/10 23:54 , Charlie Clark wrote:
I propose to add Site Syndication Settings to the actions/global and
remove the Properties form from the SyndicationTool. I also think that
synPropertiesForm should be moved to actions/folder and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/30/10 14:37 , Marius Gedminas wrote:
http://docs.zope.org/zopetoolkit/process/buildbots.html shows a very
neatly organized overview of the status of various buildbots.
There's only one problem: the content is outdated (Last updated on Sep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Charlie,
enable_permalink. Now, while this is easy enough to add both to the
Script and my view and there is support for this in
zpt_generic/main_template with get_permalink, there is actually an
implicit dependency about CMFUid for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/22/10 20:49 , Charlie Clark wrote:
Am 22.09.2010, 14:31 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Are there any outstanding issues or blockers that need resolving or can
I go ahead and publish the new releases?
While I'd like my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:39 , Charlie Clark wrote:
Hi,
Yuppie brought this up at the Dresden Sprint: does anyone have any
objections to removing the ursa and werebear skins in 2.3? Both are
just examples of using a BrowserView for the tool lookups and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:36 , Charlie Clark wrote:
Am 23.09.2010, 10:40 Uhr, schrieb yuppie y.2...@wcm-solutions.de:
Are you sure you want to make these changes in CMF 2.1? Jens is not
talking about CMF 2.2 or trunk.
Oh, yeah. Sorry, so caught up in 2.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 12:38 , yuppie wrote:
My goal is to have *one* branch for each CMF version. (Except of CMF
2.1, which has also a non-buildout branch.) I think we have always a
primary target platform that is used for development (e.g. Zope trunk
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on the following bugs:
Already fixed
=
https://bugs.launchpad.net/products.zsqlmethods/+bug/440993
Fixed
=
https://bugs.launchpad.net/products.zsqlmethods/+bug/142689
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/25/10 21:32 , Vladislav Vorobiev wrote:
ps: my normal email for this mailings list is **mymir@gmail.com**. I
subscribe the list and get emails but I can't send anything. No mail
from mymir@gmail.com was accept
Log message for revision 115797:
- LP #193122: New method getVirtualRoot added to the Request class
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/ZPublisher/HTTPRequest.py
U Zope/branches/2.12/src/ZPublisher/tests/testHTTPRequest.py
-=-
Modified:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/19/10 09:46 , Hanno Schlichting wrote:
Can roles currently contain whitespace? Like Awesome People?
If so, we should go for nested nodes:
permission id=my.NewPermission title=My new permission
roleManager/role
roleSiteAdmin/role
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/11/10 14:44 , Baiju M wrote:
Hi,
I think the cron job or script not working. Now
the documentation site is not getting updated:
http://bluebream.zope.org/doc/1.0/index.html
Who is having access to check docs.zope.org,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/9/10 08:58 , Baiju M wrote:
On Thu, Apr 8, 2010 at 8:39 PM, Baiju M mba...@zeomega.com wrote:
Hi,
What about retiring zope3-checkins list ?
I send this sometimes back. What needs to be
done to retire this list ? I think there are few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 00:16 , Willi Langenberger wrote:
According to Jens Vagelpohl:
before=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4)
svn up -q $ROOT
after=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4)
I think
svn info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 16:52 , yuppie wrote:
Charlie Clark wrote:
I'm actively abstaining as while I understand the need to clean things up,
I'm not sure I understand the whole context (my lack of understanding
rather than any lack of explanation). CMF is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chris,
I've just been doing some build and release tools for a customer that
involve this sort of stuff, I resorted to:
snip lots of code
Yikes. Maybe the subshell isn't so bad after all :-P
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 10:52 , Hanno Schlichting wrote:
Hi.
On Wed, Aug 4, 2010 at 10:31 AM, Chris Withers ch...@simplistix.co.uk wrote:
I'm in the process of egg-ifying some Zope 2 Products of mine (first up
is MailTemplates) and I'm curious as to how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 11:33 , Chris Withers wrote:
Jens Vagelpohl wrote:
I've just been doing some build and release tools for a customer that
involve this sort of stuff, I resorted to:
snip lots of code
Yikes. Maybe the subshell isn't so bad after all :-P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 14:55 , Marius Gedminas wrote:
On Wed, Aug 04, 2010 at 11:09:58AM +0200, Jens Vagelpohl wrote:
On 8/4/10 10:57 , Adam GROSZER wrote:
Hello Jens,
Something is wrong with the automatic update of
http://docs.zope.org/zopetoolkit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 17:26 , Wichert Akkerman wrote:
I'm wondering: can it be made to skip useless docs such as
http://docs.zope.org/zope.hookable/index.html, perhaps by checking for
linecount?
There are also a lot of packages that only have a changelog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
Do you have access to an source distribution (tarball or zip) for the
package involved?
In the source distribution the PKG-INFO file is always at the top level.
No, these are trunk checkouts.
jens
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/10 00:19 , Tres Seaver wrote:
The 'pkginfo' utility knows how to extract package metadata from stuff
installed on the path:
http://packages.python.org/pkginfo/distributions.html#introspecting-installed-packages
as well as from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 15:51 , Stephan Richter wrote:
We have put a lot of energy into putting the full documentation of packages
into the package's long description and most packages have this layout (I
know, because I did it for most. ;-) So it might be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/10 22:59 , Marius Gedminas wrote:
On Tue, Aug 03, 2010 at 10:42:42PM +0200, Jens Vagelpohl wrote:
listing, like the ZTK list[1]. I had to resort to executing setup.py
--long-description in a subprocess, unfortunately. Never found out how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martijn,
http://docs.zope.org/zope.event/
Really cool!
Wouldn't it be good to put this under /package/zope.event to avoid
potential naming conflicts? I realize they're rare, but I can imagine
that a project foo could exist that wants to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 14:00 , Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Sun Aug 1 12:00:00 2010 UTC to Mon Aug 2 12:00:00 2010 UTC.
There were 91 messages: 6 from Zope Tests, 1 from buildbot at
enfoldsystems.com, 4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 15:51 , Stephan Richter wrote:
We have put a lot of energy into putting the full documentation of packages
into the package's long description and most packages have this layout (I
know, because I did it for most. ;-) So it might be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:36 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
'll have to look at that. Currently, the documentation builder does not
do any introspection on the package itself, mostly because I do not want
to fully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:48 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
Thanks for the hint, I'll try that. Can you give me a sample package
where the long description is supposed to be the main documentation? And
what's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:50 , Stephan Richter wrote:
On Monday, August 02, 2010, Stephan Richter wrote:
py26 setup.py --long-description | rst2html
rst2html have many options that allow you to modify the style, including
the ability to specify a stylesheet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 17:00 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
OK, I'll see what I can do with that. I'll probably end up using the
long description as last fallback. So you will see every package linked
to *something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:36 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
'll have to look at that. Currently, the documentation builder does not
do any introspection on the package itself, mostly because I do not want
to fully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 18:26 , Martijn Faassen wrote:
http://packages.python.org/distribute/pkg_resources.html
You can probably create a Distribution object somehow (handwave) from a
path (whether that's the path of the package or the path the package is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Here's a followup on a docs.zope.org automation task I took over during
one of the Zope developer IRC metings[1]. The task was to provide
individual package documentation, if it exists, directly underneath
docs.zope.org, e.g.:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: FAILED (failures=15) : CMF-2.2 Zope-2.12 Python-2.6.5 : Linux
From: CMF Tests
Date: Thu Jul 29 21:57:59 EDT 2010
URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013347.html
Subject: FAILED (failures=15) : CMF-trunk Zope-2.12
Log message for revision 115201:
- update DateTime to 2.12.5
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/versions.cfg
-=-
Modified: Zope/branches/2.12/doc/CHANGES.rst
===
---
Log message for revision 115202:
- update DateTime to 2.12.5
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/versions.cfg
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst 2010-07-29 11:32:07
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/29/10 15:57 , yuppie wrote:
Hanno Schlichting wrote:
On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspelioptilude+li...@gmail.com
wrote:
On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote:
Sure. But do you always run all tests it picks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michele,
I would consider the coincience with strace reviving the process a red
herring. When strace runs it does not influence the process you are
watching with it, except for telling you what OS-level calls are made.
The most common reason for
I cannot access the files. Apparently you must have a Google account and log in
:-(
jens
On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote:
On Jul 16, 2010, at 3:28 PM, Christian Theune wrote:
- We need to deal with the fact that some projects in svn.zope.org are
likely
tested with different browsers without login and I could download
files.
Google account should not be required.
Do you mean you cannot see the listing of files when you accessed to that URL
in your browser?
Takeshi
On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote:
I cannot access
of download
link.
The download link is located just under the file name per file.
Takeshi
On Jul 18, 2010, at 7:07 PM, Jens Vagelpohl wrote:
Hi Takeshi,
I can see the listing but when I click on a file download link I get a page
saying insufficient privileges. You must be logged in to view
Log message for revision 114771:
- update to DocumentTemplate 2.13.1
(https://bugs.launchpad.net/zope2/+bug/143273)
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/versions.cfg
-=-
Modified: Zope/trunk/doc/CHANGES.rst
Log message for revision 114737:
- LP #143564: Request.resolve_url did not correctly re-raise
exceptions encountered during path traversal.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/ZPublisher/HTTPRequest.py
U Zope/trunk/src/ZPublisher/tests/testHTTPRequest.py
Log message for revision 114738:
- LP #143722: Added missing permission to ObjectManager.manage_hasId,
which prevented renaming files and folders via FTP.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/OFS/ObjectManager.py
-=-
Modified:
Log message for revision 114739:
- LP #143722: Added missing permission to ObjectManager.manage_hasId,
which prevented renaming files and folders via FTP.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/OFS/ObjectManager.py
-=-
Modified: Zope/trunk/doc/CHANGES.rst
Log message for revision 114741:
- LP #143533: Instead of showing 0.0.0.0 as server name when no
specific listening IP is configured for the HTTP server, do a
socket lookup to show the current server's fully qualified name.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 114742:
- LP #143533: Instead of showing 0.0.0.0 as server name when no
specific listening IP is configured for the HTTP server, do a
socket lookup to show the current server's fully qualified name.
Changed:
U Zope/trunk/doc/CHANGES.rst
U
Log message for revision 114746:
- LP #143755: Also catch TypeError when trying to determine an
indexable value for an object in PluginIndexes.common.UnIndex
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/Products/PluginIndexes/common/UnIndex.py
U
Log message for revision 114747:
- LP #143755: Also catch TypeError when trying to determine an
indexable value for an object in PluginIndexes.common.UnIndex
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/Products/PluginIndexes/common/UnIndex.py
U
Log message for revision 114752:
- refining the fix for LP #143533
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/ZServer/HTTPServer.py
-=-
Modified: Zope/branches/2.12/doc/CHANGES.rst
===
---
Log message for revision 114753:
- refining the fix for LP #143533
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/ZServer/HTTPServer.py
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/10 16:28 , Wichert Akkerman wrote:
On 7/14/10 16:19 , Jens Vagelpohl wrote:
Log message for revision 114741:
- LP #143533: Instead of showing 0.0.0.0 as server name when no
specific listening IP is configured for the HTTP server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/10 17:00 , Andreas Jung wrote:
Wichert Akkerman wrote:
I don't mind doing this for a SERVER_NAME in the response, but looking
at the diff from the commit email you also changed the startup message
from Zope 2 with this change. That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on Zope2 bugs today. This is what I managed to get done:
Fixed
=
- https://bugs.launchpad.net/zope2/+bug/143273
- https://bugs.launchpad.net/zope2/+bug/143564
- https://bugs.launchpad.net/zope2/+bug/143722
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/6/10 17:53 , Christian Theune wrote:
So, next Wednesday (2010-07-14) is the next bug day. Here's a wiki page
so you can also register there to indicate participation:
http://wiki.zope.org/ztk/BugDay20100714
I'll not that the simple table you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/4/10 10:41 , Adam GROSZER wrote:
Hello Shane,
Are you the list admin there or you know who it is?
Hi Adam,
I just looked and Shane's no longer working zope.com address was listed
as the only admin. I put myself in instead.
Do you need me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/4/10 13:46 , Hanno Schlichting wrote:
On Sun, Jul 4, 2010 at 11:30 AM, Jens Vagelpohl j...@dataflake.org wrote:
As you may have seen from the checkins, I have done a CMF 2.2 point
release. Hanno said this would help Plone 4 testing.
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/1/10 17:36 , Martin Aspeli wrote:
On 1 July 2010 21:10, Godefroid Chapelle got...@bubblenet.be wrote:
http://packages.python.org/z3c.form
Who will get rid of http://docs.zope.org/z3c.form/ ?
If you do, can you please make it link or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/10 09:30 , Chris Withers wrote:
Tres Seaver wrote:
The misconfiguration of the mail host in transactional mode *does* cause
the server to go into a lockdown mode (because errors are not supposed
to be raised in 'tpc_finish'). There is
Log message for revision 113513:
- LP #143946: Provide a more informative error message when a
WebDAV PUT fails.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/webdav/NullResource.py
U Zope/branches/2.12/src/webdav/tests/testNullResource.py
-=-
Log message for revision 113514:
- LP #143946: Provide a more informative error message when a
WebDAV PUT fails.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/webdav/NullResource.py
U Zope/trunk/src/webdav/tests/testNullResource.py
-=-
Modified:
Log message for revision 113515:
- LP #374818: Use module-provided functions as opposed to the old
folder methods when creating folders and user folders in
ZopeTestCase.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 113516:
- LP #374818: Use module-provided functions as opposed to the old
folder methods when creating folders and user folders in
ZopeTestCase.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/Testing/ZopeTestCase/ZopeTestCase.py
-=-
Modified:
Log message for revision 113517:
- LP #142535: Fix faulty docstring for manage_changeProperties which
incorrectly suggested that passing a simple dictionary as REQUEST
argument was supported.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 113518:
- LP #142535: Fix faulty docstring for manage_changeProperties which
incorrectly suggested that passing a simple dictionary as REQUEST
argument was supported.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/OFS/PropertyManager.py
U
Log message for revision 113562:
- LP #143619: Make sure to remove a RAMCache's contents when the
ZODB object is removed.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Zope/branches/2.12/src/Products/StandardCacheManagers/AcceleratedHTTPCacheManager.py
U
Log message for revision 113563:
- LP #143619: Make sure to remove a RAMCache's contents when the
ZODB object is removed.
Changed:
U Zope/trunk/doc/CHANGES.rst
U
Zope/trunk/src/Products/StandardCacheManagers/AcceleratedHTTPCacheManager.py
U
Log message for revision 113567:
- LP #143639: When the last cache manager in a container is
deleted, we need to remove all traces of it from the
container.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/OFS/Cache.py
A
Log message for revision 113568:
- LP #143639: When the last cache manager in a container is
deleted, we need to remove all traces of it from the
container.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/OFS/Cache.py
A Zope/trunk/src/OFS/tests/testCache.py
-=-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Unknown to the Zope Foundation and the ZF admins it appears the zope.org
and zopefoundation.org domains have expired. The domains were held by
Rob Page as Zope Corporation representative.
For community members this means services like the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on Zope2 bugs today. This is what I managed to get done:
Fixed
=
https://bugs.launchpad.net/zope2/+bug/143946
https://bugs.launchpad.net/zope2/+bug/374818
https://bugs.launchpad.net/zope2/+bug/142535
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Unknown to the Zope Foundation and the ZF admins it appears the zope.org
and zopefoundation.org domains have expired. The domains were held by
Rob Page as Zope Corporation representative.
For community members this means services like the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/16/10 13:51 , Jens Vagelpohl wrote:
Hi all,
Unknown to the Zope Foundation and the ZF admins it appears the zope.org
and zopefoundation.org domains have expired.
Hi all,
The situation has being resolved.
It turns out only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/3/10 16:29 , Tres Seaver wrote:
Zope Tests Summarizer wrote:
Subject: FAILED : Zope Buildbot / zope2.12 slave-osx
From: jdriessen at thehealthagency.com
Date: Wed Jun 2 09:33:54 EDT 2010
URL:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reminder:
Today at 20:00 UTC (less than 12 hours from now) one of the Zope
Foundation-maintained servers will be physically moved to a different
data center by our hosting provider. The server will be shut down at
around 20:00 UTC and, according to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reminder:
Today at 20:00 UTC (less than 12 hours from now) one of the Zope
Foundation-maintained servers will be physically moved to a different
data center by our hosting provider. The server will be shut down at
around 20:00 UTC and, according to
101 - 200 of 1121 matches
Mail list logo
