I am using buildout (following the buildout tutorial at plone.org) to install Plone 2.5.5 on a Centos 5 server. My buildout is able to download and set everything up. However, I have problems in starting my primary instance.
Running ./bin/primary fg results in an import error. The system returned: ---------------------------------------------- 2008-06-12 08:47:15 INFO Zope Set effective user to "plone" Traceback (most recent call last): File "/root/src/plone-2.5.5/parts/zope2/lib/python/Zope2/Startup/run.py", line 56, in ? File "/root/src/plone-2.5.5/parts/zope2/lib/python/Zope2/Startup/run.py", line 21, in run File "/usr/lib/python2.4/site-packages/PIL/__init__.py", line 95, in prepare File "/usr/lib/python2.4/site-packages/PIL/__init__.py", line 272, in makeLockFile ImportError: No module named misc.lock_file --------------------------------------------- The problem is similar to posts from: http://www.gossamer-threads.com/lists/zope/users/197218?page=last http://www.nabble.com/Plone3%3A-some-problems-using-buildout-td14400927s15482.html#a14694830 However, no fix was reported. My Centos 5 system has the following versions of python: python-2.4.3-19.el5 python-imaging-1.1.5-5.el5 I tried the same buildout configuration on Debian Etch with python 2.4.4-2 and python-imaging 1.1.5-11. Just like in my Centos box, the Debian buildout was able to install Plone 2.5.5 successfully. But in Debian, I had no problems with lock_file.py and my instance executed without a problem. Any ideas how to solve this issue? Thanks. Holden Hao
_______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
