On Sun, Jul 11, 2010 at 3:18 PM, John Griessen wrote:

I've been making a buildout.cfg for deploying web sites and hit some snags.

django-page-cms is a package I want, and getting it via buildout found eggs for other apps, but needed source for django-page-cms.

I don't know what this means.

From there, some requirements, (don't know where they are in the code), pulled in packages django-haystack, django-messages, whoosh, django-mptt-2, and coverage.

I think to build the source only absolutely requires django-mptt-2.

Buildout pulls in the run-time requirements, as defined in the packages install_requires.

whoosh and coverage have had problems.  buildout found whoosh as a zipped egg and left it zipped even though putting it in the common eggs directory where all others are unzipped and a python path points to them for use when code runs.  To get a complete build, I manually unzipped.

Include: unzip = true in the buildout section of your buildout. ...

coverage was found OK from my local machine, but not from the server. I'm not sure yet why.

I'll try using bin/buidout -D  (Debug errors.)  soon.

Any other suggestions?

Try running with -v (verbode) or -vv (debug/very verbose) Jim -- Jim Fulton