So, trying to build pound through a Buildout recipe was failing part of the way through.

Two problems and their solutions (not necessarily in that order):

• Needed to install libssl-dev because lcrypto was missing (ambiguity anyone?) – Synaptic says that the package provides “libssl and libcrypto development libraries, header files and manpages” (but never mind a search for `libcrypto`…)
• Had to correct the relevant user that the recipe was telling pound to build as.

The first point was pretty silly and the second one was just clearly my copy-and-paste mistake.

Two blog entries in one day – wow it’s been a good work day.

Just a quick chronicle of my thoughts: version conflicts in buildout aren’t always pretty. My latest escapade into trying to load up Varnish through zc.buildout resulted in a hair-tearing out message:

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1477, in main
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 346, in install
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 857, in getitem
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 938, in _initialize
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 901, in _install_and_load
File "/usr/lib/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resources.py", line 277, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resources.py", line 2179, in load_entry_point
raise ImportError("Entry point %r not found" % ((group,name),))
ImportError: Entry point ('zc.buildout', 'default') not found

What??? What’s that supposed to mean?

Turns out I managed to stumble upon the cause: our local PyPi repository had actually already had an old version of the plone.recipe.varnish source on it and my buildout needed the latest version. Even though I’d directed buildout to seek out such version, my cache folder already thought it was satisfied.

Solution

Remove the old version from the cache and stick the new version into the local PyPi.

So it’s almost Christmas time and I’m still slaving away working. It’s all about commitment.

Today in my life I’ve been trying to install the OpenXml product for Plone (using buildout, of course).

david@computer:~/buildout/instance$ ./bin/buildout
Uninstalling zopepy.
Uninstalling instance.
Updating plone.
Updating zope2.
Updating productdistros.
Installing instance.
Getting distribution for 'Products.OpenXml'.
Got Products.OpenXml 1.0.1.
Getting distribution for 'openxmllib'.
Got openxmllib 1.0.3.
Getting distribution for 'lxml>=1.3.0,<2.0.0dev'.
Building lxml version 1.3.6
ERROR: /bin/sh: xslt-config: not found
** make sure the development packages of libxml2 and libxslt are installed
**ERROR: /bin/sh: xslt-config: not found
** make sure the development packages of libxml2 and libxslt are installed
**ERROR: /bin/sh: xslt-config: not found

And then 50,000 errors follow, making this message hard to find. Either way, the end result was that lxml wasn’t able to install.

Solution: install libxslt and its dev counterpart plus the relevant Python bindings on your system. In Ubuntu 8.10, that’s libxslt1.1, libxslt1-dev, and python-libxslt1.

All good now.

Update: Turns out Centos 5 (Red Hat) is has different package names. Try yum install libxslt libxslt-devel libxslt-python as root for Centos.