-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
Quick test, please ignore
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkv/WJkACgkQRAx5nvEhZLJ4oACgm3AmtfWAwvrhVvB83AxcbHfJ
EdkAoLTWC5DeBS3xsls8FTCPU5UEZIgu
=q806
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/26/10 14:05 , Hanno Schlichting wrote:
This looks like its caused by Jens cleanup in Zope2:
Error in test test_manage_propertiesForm_allows_adding
(Products.CMFCore.tests.test_ActionInformation.ActionTests)
Traceback (most recent call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note:
First of all, apologies for the cross-posting. I wanted to reach as many
people as possible.
On Thursday, May 27 (2 days from now) one of the Zope
Foundation-maintained servers will be physically moved to a different
data center by our
Log message for revision 112683:
- LP #142874: Naming objects ``URL`` or ``URL1`` broke several ZMI
views.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/App/dtml/manage.dtml
U Zope/branches/2.12/src/App/dtml/manage_tabs.dtml
U
Log message for revision 112684:
- LP #142874: Naming objects ``URL`` or ``URL1`` broke several ZMI
views.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/App/dtml/manage.dtml
U Zope/trunk/src/App/dtml/manage_tabs.dtml
U Zope/trunk/src/OFS/dtml/fileEdit.dtml
U
Log message for revision 112687:
- LP #143261: The (very old-fashioned) Zope2.debug interactive request
debugger still referred to the toplevel module ``Zope``, which was
renamed to ``Zope2`` a long time ago.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 112688:
- LP #143261: The (very old-fashioned) Zope2.debug interactive request
debugger still referred to the toplevel module ``Zope``, which was
renamed to ``Zope2`` a long time ago.
Changed:
U Zope/trunk/doc/CHANGES.rst
U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note:
First of all, apologies for the cross-posting. I wanted to reach as many
people as possible.
On Thursday, May 27 (2 days from now) one of the Zope
Foundation-maintained servers will be physically moved to a different
data center by our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note:
First of all, apologies for the cross-posting. I wanted to reach as many
people as possible.
On Thursday, May 27 (2 days from now) one of the Zope
Foundation-maintained servers will be physically moved to a different
data center by our
Log message for revision 112511:
- LP #142226: Added an extra keyword argument to the HTTPResponse
setCookie method to suppress enclosing the cookie value field
in double quotes.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/Products/OFSP/help/Response.py
U
Log message for revision 112512:
- LP #142226: Added an extra keyword argument to the HTTPResponse
setCookie method to suppress enclosing the cookie value field
in double quotes.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 112513:
- LP #142451: If non-recursive ownership changes are made using
``changeOwnership``, do not touch any children.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/AccessControl/Owned.py
U Zope/trunk/src/AccessControl/tests/testOwned.py
Log message for revision 112514:
- LP #142451: If non-recursive ownership changes are made using
``changeOwnership``, do not touch any children.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/AccessControl/Owned.py
U
Log message for revision 112530:
- LP #142750 and LP #142481: To prevent confusion when choosing an Id and
to avoid issues when creating two VirtualHostMonsters in the same
container the VirtualHostMoster now has a default Id. It can no longer
be selected, and the intermediary Add
Log message for revision 112531:
- LP #142750 and LP #142481: To prevent confusion when choosing an Id and
to avoid issues when creating two VirtualHostMonsters in the same
container the VirtualHostMoster now has a default Id. It can no longer
be selected, and the intermediary Add
Log message for revision 112536:
- LP #142590: The ``DTMLMethod`` and ``DTMLDocument`` ``manage_edit``
methods could not deal with ``TaintedString`` instances. Removed the
entirely redundant ``DTMLDocument.manage_edit`` method at the same time.
Changed:
U
Log message for revision 112537:
- LP #142590: The ``DTMLMethod`` and ``DTMLDocument`` ``manage_edit``
methods could not deal with ``TaintedString`` instances. Removed the
entirely redundant ``DTMLDocument.manage_edit`` method at the same time.
Changed:
U
Log message for revision 112542:
- LP #142410: Do not index documents in a KeywordIndex if the document
is missing the indexed attribute, if determining the value raises
AttributeError, or of the indexed attribute is empty.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U
Log message for revision 112543:
- LP #142410: Do not index documents in a KeywordIndex if the document
is missing the indexed attribute, if determining the value raises
AttributeError, or of the indexed attribute is empty.
Changed:
U Zope/trunk/doc/CHANGES.rst
U
Log message for revision 112553:
- LP #143144: Fix documentation for the zope.conf ``mount-point``
directive.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/Zope2/Startup/zopeschema.xml
-=-
Modified: Zope/branches/2.12/doc/CHANGES.rst
Log message for revision 112554:
- LP #143144: Fix documentation for the zope.conf ``mount-point``
directive.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/Zope2/Startup/zopeschema.xml
-=-
Modified: Zope/trunk/doc/CHANGES.rst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reminder:
In about 3.5 hours 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 the hosting provider, become
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please note:
First of all, apologies for the cross-posting. I wanted to reach as many
people as possible.
On Monday, May 10 (tomorrow) one of the Zope Foundation-maintained
servers will be physically moved to a different data center by our
hosting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all (and especially Lennart),
I need a quick sanity check. Trying to test a package of mine for Python
3 compatibility I built Python 3.1.2 and installed distribute into it.
My package depends on zope.interface. I am executing...
$ python3.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/2/10 21:30 , Lennart Regebro wrote:
On Sun, May 2, 2010 at 18:37, Jens Vagelpohl j...@dataflake.org wrote:
The issue is a non-ASCII character in the Changelog:
snip
- - Added support for Python 3.1. Contributors:
Lennart Regebro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft?
Like 5 years old nothing happened since then bugs.
I think we should add a tag too old, add a note to warn subscribers,
then set a status
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/22/10 11:11 , Adam GROSZER wrote:
Hello,
JV On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft?
Like 5 years old nothing happened since then bugs.
I think we should add a tag too old,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/15/10 09:58 , Tres Seaver wrote:
Sidnei da Silva wrote:
+link = ('https://bugs.launchpad.net/%s/+bug/%s'
+% (self.project_name, bug_id))
You can actually link to the bug having an id only, by using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/10 15:43 , Charlie Clark wrote:
Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Needless to say, this is more useful when using a CookieCrumbler as a
standalone object without a portal. The CMF does not need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 10:54 , Charlie Clark wrote:
That warning should not show up for type-specific Actions. They are not
deprecated. This is a bug.
I'll remove it from editToolsActions.dtml then. Can we backport this to
CMF 2.2?
Sure.
In my work on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 11:09 , Charlie Clark wrote:
Am 09.04.2010, 10:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
I'll remove it from editToolsActions.dtml then. Can we backport this to
CMF 2.2?
Sure.
Committed to trunk. For 2.2 do I just make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 13:29 , Charlie Clark wrote:
Any idea why CookieCrumbler is a Folder?
They can contain objects that can be used as login/logout pages, such as
DTML methods or Page Templates.
Needless to say, this is more useful when using a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 17:08 , Tres Seaver wrote:
I'm seeing frequent periods of 50+% packet loss to the machine, and
can't even get top to run on it this morning. Any clues about what is
causing the load?
I haven't watched it because I don't know when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 17:27 , Jim Fulton wrote:
We've been having some networking issues over the last week or two that
we believe to have been addressed.
I'm still getting alerts from Nagios 2-3 times a day caused by high
packet loss and inability to connect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 13:09 , Charlie Clark wrote:
Hi,
I'm currently working on a project which will hopefully have no TTW code
so I was hoping to be do without skins - currently I have a my skin on top
of CMFDefault but it is just main_template and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:10 , yuppie wrote:
IIRC the general policy for the Zope repository is to switch to relative
externals after the release of Ubuntu 10.04 LTS, but I guess all people
using CMF.buildout have already Subversion =1.5 available.
Huh?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:28 , yuppie wrote:
Jens Vagelpohl wrote:
On 4/1/10 12:10 , yuppie wrote:
IIRC the general policy for the Zope repository is to switch to relative
externals after the release of Ubuntu 10.04 LTS, but I guess all people
using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 20:33 , Tres Seaver wrote:
I also don't know why the 'instance' and 'i18n*' parts are configured in
these buildouts -- does somebody have a memory of why, or a reason to
keep them?
The instance part is a pure convenience to quickly fire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 22:07 , Tres Seaver wrote:
Jens Vagelpohl wrote:
On 3/31/10 20:33 , Tres Seaver wrote:
I also don't know why the 'instance' and 'i18n*' parts are configured in
these buildouts -- does somebody have a memory of why, or a reason to
keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/18/10 09:23 , Godefroid Chapelle wrote:
As far as I know, Zope 2 has no release manager since Andreas retired
after so many years of hard work.
I think there is a need for a new release manager.
Is that question part of the horizon of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/10/10 15:53 , Lennart Regebro wrote:
On Tue, Feb 9, 2010 at 08:19, Marius Gedminas mar...@gedmin.as wrote:
Well, technically I suppose we're all violating the law by not following
the ZPL requirement of keeping the licence text next to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/9/10 22:23 , Charlie Clark wrote:
Am 09.02.2010, 13:46 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
Your event handler handle_new_masterpage should be rewritten to look
if the object it wants to instantiate already exists. If it exists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/24/10 13:08 , Baiju M wrote:
Hi,
I would like to know the legal formalities required
to accept a logo (with special font).
Also I would like to know the same for web design.
Is there any guideline for Zope Foundation ?
BlueBream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andreas,
I would like to inform you that I intent to retreat from the Zope 2
release manager position soon. I have been serving the Zope community in
this position for almost seven years and now it is time to move on and
hand
over the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Jan Ulrich Hasecke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.10 08:36, Martin Aspeli wrote:
+1. It puts the final nail in the Zope 3 coffin and allows a reborn
vampire to emerge from slumber.
Ok, we all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader than Zope2,
Grok,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
Jan Ulrich Hasecke wrote:
On 04.01.10 19:23, Baiju M wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
Coming from marketing I strongly suggest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
Hi there,
we have some huge ZODB file storage (60-80 GB each) and we want
to split the storage into a number of smaller storage (easier
to handle for backup and packing). The storages themselves only
contain a few (Zope 2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
On 2009-12-30 15:06, Jens Vagelpohl wrote:
Separate note: On the Import tab I see a dropdown of extension
profiles to select. Changing the selection here never affects the list
of available import steps, though
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
We have three perspectives:
* the ZTK is new, therefore the ZTK doesn't need to care about Zope 3 at
all.
+1
* the ZTK is a renamed, refocused Zope 3, therefore the ZTK needs to
care about Zope 3.
- -1
* both: the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Pharis wrote:
I have several existing Z2 Products that aren't going anywhere. I still need
these. I can't just move to Z3 and leave our existing Z2 Products behind.
There seems to be a misunderstanding what the ZTK is and what it isn't.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Pharis wrote:
Yes, I'm running into missing bits in various places. So even though Z2.12
is based on ZTK eggs, and ZTK eggs are designed using all the CA goodness, I
still can't easily develop using those methods. So I'm left leaving this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Pharis wrote:
browser:containerViews
for=Test.interfaces.INewTestSite
contents=zope.ManageContent
index=zope.View
add=zope.ManageContent
/
ZopeXMLConfigurationError: File
On Nov 29, 2009, at 11:59 , Gaute Amundsen wrote:
Quick question before I reinvent.
Is there some established way of finding products which have no
instances in zodb, and can be safely removed?
No there isn't. You may have to invest some time writing a script that visits
all objects to
Log message for revision 105093:
- correct link to the Zope2 Book
Changed:
U Zope/trunk/src/App/dtml/zope_quick_start.dtml
-=-
Modified: Zope/trunk/src/App/dtml/zope_quick_start.dtml
===
---
Log message for revision 105094:
- fix link to Zope2 book
Changed:
U Zope/branches/2.12/src/App/dtml/zope_quick_start.dtml
-=-
Modified: Zope/branches/2.12/src/App/dtml/zope_quick_start.dtml
===
---
On Oct 15, 2009, at 19:02 , Baiju M wrote:
Hi Jens,
In Zope 2.12, we have given a link to :
http://docs.zope.org/zope2book/
from the main page displayed after installation (index_html).
It's redirecting to old page which we have changed few days
back. Can you please change the
On Oct 10, 2009, at 06:22 , Baiju M wrote:
Hi Jens,
I was looking at Zope 2 documentation. To generate this
site :
http://docs.zope.org/zope2/
we use the buildout available here, is it ?
svn://svn.zope.org/repos/main/zope2docs/trunk
Yes.
So, can I remove the buildout
On Oct 10, 2009, at 11:15 , Baiju M wrote:
Also where I need to make change to fix docs.zope.org
I will make those. That front page is not in SVN anywhere, it's just
one file on the file system.
jens
smime.p7s
Description: S/MIME cryptographic signature
On Oct 10, 2009, at 11:15 , Baiju M wrote:
Also I removed the 'sources' directory and moved all docs one level
up.
This will shorten the URL. But now I realized that it's going
to break few URLs in these places:
http://docs.zope.org/
http://zope2.zope.org/resources/documentation
Should I
On Oct 7, 2009, at 12:30 , Michael Haubenwallner wrote:
Forwarding an email - what do you think?
Regards
Michael
Milind Khadilkar wrote:
Hi,
I have pointed zope2.org to zope2.zope.org
If there is any objection to it, please let me know and I will
remove it.
That's very nice of him,
On Oct 7, 2009, at 16:16 , Lennart Regebro wrote:
2009/10/7 Andreas Jung li...@zopyx.com:
It's just a redirect - so I don't see much problems with that.
Yeah, so long as nobody starts advertising that address widely it's
not a problem.
No one needs to advertise it actively, search engines
On Sep 24, 2009, at 14:01 , Charlie Clark wrote:
Am 24.09.2009, 13:52 Uhr, schrieb Andreas Jung li...@zopyx.com:
In my understanding: packages using the Products namespace are
subject
to be registered during the startup phase of Zope (using their
initialize()
method). And I think there is
On Sep 24, 2009, at 15:16 , Maurits van Rees wrote:
Personally, I am the maintainer of Products.Poi. It will take more
than one bottle of whisky to convince me to rename that. ;-)
Personally, I believe most product authors who have a real Zope 2
Product but chose a name other than
On Sep 24, 2009, at 14:17 , Charlie Clark wrote:
Regarding something completely different - I picked up on zope-dev
that
the svn server has been updated. Does this mean that we can now use
the
svn branch to trunk merging offered in svn = 1.5 or is this still
inadvisable? If it is still
On Sep 21, 2009, at 18:47 , Martijn Faassen wrote:
So, I'd be against any you can't contribute documentation unless it's
executable rule. The value of narrative documentation is tremendous,
automatically checked or not. Hopefully there are also iterative
ways to
get from non-executable to
On Sep 9, 2009, at 15:30 , Martijn Faassen wrote:
Ah, I perhaps misunderstood. I figured the resolving of relative
externals would be a problem with a Subversion 1.4.x client.
There's two different issues being confused here.
SVN 1.4 clients will work with SVN 1.5 repositories in general.
On Sep 9, 2009, at 15:59 , Sidnei da Silva wrote:
On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohlj...@dataflake.org
wrote:
SVN 1.4 clients will work with SVN 1.5 repositories in general.
However,
that's not the real issue here. The issue is the new-style externals
definitions that
On Sep 9, 2009, at 17:05 , Martijn Faassen wrote:
Jens Vagelpohl wrote:
SVN 1.4 clients will work with SVN 1.5 repositories in general.
However,
that's not the real issue here. The issue is the new-style externals
definitions that allow you to use relative paths. Those relative
paths
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2009, at 04:33 , Miguel Beltran R. wrote:
OPERATIONS_ERROR: {'info': ': LdapErr: DSID-0C090627,
comment: In
order to perform this operation a successful bind must be completed
on the
connection., data 0, vece', 'desc':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 2, 2009, at 10:09 , Kedar Dash wrote:
Let us keep this performance/ maintenance issue aside. is there a
way where by this feature can be disabled so that zope does not log
this at all.
No there is not.
jens
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 15, 2009, at 19:03 , Alec Mitchell wrote:
There's one additional significant change to Zope behavior here that
I forgot to mention. The current implementation sets the python
default email transfer and header encoding for 'utf-8'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 14, 2009, at 06:22 , Alec Mitchell wrote:
It would be very helpful to have these changes in Zope 2.12;
otherwise, Plone 4.0 will be stuck with our unmaintained
SecureMailHost product for yet another release in order to provide
equivalent
On Aug 13, 2009, at 5:12, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 for the approach in general (I haven't looked at the patch in
detail). Assuming all tests pass, and that you have a test
exercising
the ':' bug you describe, I would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 7, 2009, at 08:36 , Michael Haubenwallner wrote:
Hi, disk is full again.
Last successful transaction was at 2009-08-07 12:50:24 AM systemtime.
As predicted, the disk was full when the pack process finished. I'm
surprised it did finish at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 7, 2009, at 11:52 , Jim Fulton wrote:
We're going to replace the hardware, and when we do, we'll have a much
larger disk. I think we have enough disk space for now as long as we
don't pack.
Who is making sure that any automated pack cron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 6, 2009, at 09:43 , Andreas Jung wrote:
Same issue this morning. This must be fixed soon - otherwise we can
not
proceed with the releases.
I just looked and for some strange reason the ZODB has grown to over
30 GB, which means it more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 6, 2009, at 17:44 , Jim Fulton wrote:
Jens,
We're doing this. (Actually, we're going to copy the backups to
another disk first.)
We're also going to upgrade the hardware and switch to using ZRS.
Sorry, I should have acked sooner. Bad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 3, 2009, at 18:01 , Andreas Jung wrote:
We run out of disk space for the zope.org site.
Does this error still occur? I see 12 GB free on that drive, but
there's two other people who logged in before me, maybe they deleted
something.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 3, 2009, at 19:22 , David Lawson wrote:
Joseph and I both cleaned off some things. I also modified the repozo
backup cleanup script to only keep six days of backups, otherwise we
would have run out of space again either in a week or the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 3, 2009, at 19:25 , Andreas Jung wrote:
On 03.08.09 19:24, Jens Vagelpohl wrote:
On Aug 3, 2009, at 19:22 , David Lawson wrote:
Joseph and I both cleaned off some things. I also modified the
repozo
backup cleanup script to only keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 8, 2009, at 10:31 , Michael Haubenwallner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi, just got an [Errno 28] No space left on device
when adding a new user account.
Could you please look into this?
I noticed that there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
This is a heads-up that affects anyone accessing the SVN repositories
using the svn:// protocol (so it does not affect anyone accessing SVN
over HTTP, or svn+ssh):
So far the svn service was run through xinetd. We had recurring
will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin
will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2009, at 19:01 , Wichert Akkerman wrote:
Are you sending receipt confirmations? I submitted an updated
agreement
a while ago, but never got a response, so I am unsure at the moment if
it was received or if I still need to take
will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2009, at 19:01 , Wichert Akkerman wrote:
Are you sending receipt confirmations? I submitted an updated
agreement
a while ago, but never got a response, so I am unsure at the moment if
it was received or if I still need to take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 12, 2009, at 07:40 , Ian McCracken wrote:
Recently upgraded from PAS 1.4 to 1.5.3 (and Zope 2.8.8 to 2.11.2).
I'm having a new problem with basic auth; namely, that basic auth
information is ignored when using wget. Browsers work fine, ZMI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 28, 2009, at 13:08 , Martijn Faassen wrote:
What do people think about:
* the idea of renaming Site to Locus
I think that's a terrible name. While site at least means something
to people, locus doesn't carry any meaning in the specific
will try to contact any contributor who
has not replied at that point between June 18 and June 26, and
on June 26 checkin access will be removed for those who have not
sent in the new agreement.
Thanks again for your support!
Jens Vagelpohl
Secretary, Zope Foundation Board of Directors
[1] http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 16, 2009, at 23:01 , Wichert Akkerman wrote:
Previously Sidnei da Silva wrote:
Now for another question: how do people feel about moving Zope 3 and
CMF bugs to a similar setup. That is, bug mail goes to a separate
mailing list instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2009, at 22:53 , Sidnei da Silva wrote:
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org
wrote:
Same here. There is no reason for yet another mailing list. I see it
as needlessly duplicating what Launchpad already
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 5, 2009, at 15:58 , Andreas Jung wrote:
Hi there,
I tagged and released Zope 2.12.0 beta 1 today (basically identical
with the latest alpha but it includes ZODB 3.9.0 beta 1).
I'm trying to install the Zope2 egg (pulles in as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 5, 2009, at 17:23 , Andreas Jung wrote:
Unfortunately I can't get SVN 1.5 get working on my Mac.
SVN 1.5 from Fink works perfectly fine here.
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2009, at 12:00 , Jürgen Herrmann wrote:
/home/xlhost/zope/lib/python2.4/site-packages/
Products.CMFCore-2.1.2-py2.4.egg/Products/CMFCore/interfaces/
__init__.py,
line 47, in ?
from Interface.bridge import createZope3Bridge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 2, 2009, at 09:27 , Andreas Jung wrote:
Hi,
I tried several times to update my SVN checkouts (on different
machines). After
updating some svn:exernals, svn fails with something like
svn: warning: Error handling externals definition for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2009, at 17:47 , Andreas Jung wrote:
On 01.05.2009 17:33 Uhr, Chris Withers wrote:
Andreas Jung wrote:
We would have to maintain four different major release of Zope:
2.10, 2.11, 2.12 and 2.13.
Why? I suspect most of this work is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 25, 2009, at 20:30 , Laurence Rowe wrote:
Hi,
I've added the ZODB developers guide to the zope2docs buildout
(converting it to rst) and added another article and some more links
to
the zodb articles section, but ideally these should
201 - 300 of 1121 matches
Mail list logo
