On Tue, Dec 29, 2009 at 03:30:20PM +0100, Hanno Schlichting wrote:
2009/12/29 Marius Gedminas <marius@gedmin.as>:
I get the following error:
File "build/bdist.linux-i686/egg/Zope2/utilities/load_site.py", line 248 body = ("<html><head><title><dtml-var title_or_id></title> ^ SyntaxError: EOL while scanning single-quoted string
I already fixed that error on the 2.12 branch. But it's a bogus message generated by setuptools. It tries to compile all scripts ending in .py when building the egg. The script in question is never used anywhere and is probably some bitrot.
Ah, I thought it was something like this.
After that, it refuses to create a Data.fs and start up:
File "/home/mg/tmp/buildout-eggs/Zope2-2.12.2-py2.5-linux-i686.egg/Zope2/Startup/datatypes.py", line 273, in _mountPathError "No root database configured") ZConfig.ConfigurationError: No root database configured
Huh? Result of that load_site.py error, or a missing manual step that I should have known to do despite it being not mentioned in the installation docs?
I was brave enough to specify INSTANCEHOME as '.' in my zope.conf, because I strongly believe hardcoding absolute paths is dumb.
mg@platonas:~/src/akl-website-z2.12-experiment $ cat etc/zope.conf %define INSTANCE .
python $INSTANCE/bin/py
instancehome $INSTANCE
Well. You didn't specify a database file in your zope,conf it seems. Without a declaration, there's no database.
Makes sense, in a rather user-unfriendly way. May I suggest the documentation be amended to supply a closer-to-working zope.conf? I'm referring to this bit: http://docs.zope.org/zope2/releases/2.12/INSTALL.html#buildout-instances where I didn't notice the word "starting" in "Create a Zope configuration file starting as follows". Thanks for the very quick reply! Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development