Distribute/setuptools 0.7 bring some big changes. These changes can't be
handled by buildout's normal automatic upgrade mechanism. For this reason,
it's important to do one of the following if you're using buildout 2:
- Pin your distribute version to <0.7dev or to some other 0.6 version.
- Upgr
> Is there any plan to make new releases of Zope 2.12 and Zope 2.13
> integrating the patches that are meaningful for pure-Zope (non-Plone)
> applications ?
Plone doesn't always use the latest version of Zope. These are backports.
Matt
smime.p7s
Description: S/MIME Cryptographic Sig
Hello,
Plone recently released a security hotfix with a dozen of patches in it
[1].
With a quick glance at the source code of those fixes, it seemed several
of them directly patch Zope, not Plone-related products.
Is there any plan to make new releases of Zope 2.12 and Zope 2.13
integrati
Hi again,
I got the same error with zpasswd, so had to repeat the process with that
section of buildout.cfg, too... Thought I'd explain the specifics, while I
remember...
On Tue, 25 Jun 2013 19:44:48 +0100, Alex Leach wrote:
The buildout configuration that seemed to fix this, was to add