Re: Plone, zc.buildout, and Etch
Freddy Freeloader wrote:
Is anyone else out there using buildout to create Plone 3 installs on
I've been running into really strange errors when using buildout on
Etch which no one in the Plone community is able to help me with. I
cannot even complete a default buildout on Etch using Debian Python
packages. I can however, do this on successfully on Sid. I haven't
If I use the ez_setup.py script on Etch to to download and install the
Python setup tools package I can build a default Plone 3 install,
however, I then run into problems adding third party tools such as
Ploneboard, SimpleAttachment, and Clouseau. As I need the third party
tools for the functions they provide this isn't something I live with.
I can use the Plone Unified Installer, but would much prefer using
buildout as it is so much more flexible.
This all seems to be tied to changes made in the Debian Python
packages in Etch that have been made since January 30 of this year.
Why that date? Because I successfully used buildout on a server
running Etch on that day. I also added the above third party tools
successfully. Sometime since then something has changed in the
Debian Python packages, or so it would appear anyway.
Well, if anyone out there is wanting to use the buildout method of
installing Zope and Plone on Etch, at least for a while anyway, you're
going to either have to compile Python, PIL, and any other Python
dependencies from source code, or the the UnifiedInstallerBuildout
packages that combine the Unified Installer, buildout, and Python 2.4.4
in one package.
The Python interpreter now in Etch will not work. What exactly changed
I don't know, but it's changed sometime after 1/28/2008.
You can't just use the Unified Installer package either as it will
install successfully but any time you install 3rd party packages it
hoses the Plone site, sometimes so badly that even deleting the product
directories and restarting the instance or the cluster doesn't help.
You have to start over from scratch.