[tahoe-dev] zfec: py-expat dependency from darscsver?

Greg Troxel gdt at ir.bbn.com
Sat Jul 31 17:00:09 UTC 2010


In using my packaged version of tahoe, I tried to build it on a machine
with very few packages installed.  It seems that the darcsver or the
non-standard version of setuptools included in zfec depends on py-expat:

  File "/usr/ANONCVS/pkgsrc/converters/py-zfec/work/zfec-1.4.7/setuptools-0.6c15dev.egg/pkg_resources.py", line 1954, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/tmp/easy_install-1FAulv/setuptools_darcs-1.2.11/darcsver-1.5.1-py2.6.egg/darcsver/setuptools_command.py", line 5, in <module>
  File "/tmp/easy_install-1FAulv/setuptools_darcs-1.2.11/darcsver-1.5.1-py2.6.egg/darcsver/darcsvermodule.py", line 3, in <module>
  File "/usr/pkg/lib/python2.6/xml/parsers/expat.py", line 4, in <module>
    from pyexpat import *
ImportError: No module named pyexpat
*** Error code 1

Stop.
make: stopped in /usr/ANONCVS/pkgsrc/converters/py-zfec

Any thoughts other than packaging darcsver and expressing the
dependency?  Maybe a command-line argument to setup to avoid this?  I
don't understand what's going on that the standard setuptools isn't good
enough (pkgsrc already has that).  It seems unfortunate that just
wanting to run someting like zfec drags in expat.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100731/962a87a2/attachment.asc>


More information about the tahoe-dev mailing list