I'm using collective.recipe.patch to patch plone.recipe.zeoserver during a
buildout. The problem is that after applying the patch the py file isn't
consistently reloaded. If I look at the timestamps, I can see that the pyc
file isn't always regenerated after the patch is applied. Is there anyway to
force a reload with buildout? If I run buildout a 2nd time it then runs
fine.

TIA,

- Jim

parts = patches zeo

[patches]
recipe = collective.recipe.patch
egg = plone.recipe.zeoserver
patches = patches\plone.recipe.zeoserver.__init__.py.patch

[zeo]
recipe = plone.recipe.zeoserver
zeo-address  = ${buildout:zeo-address}
zeo-log = ${buildout:directory}\var\zeoserver\zeoserver.log
pid-file = ${buildout:directory}\var\zeoserver\zeoserver.pid
socket-name = ${buildout:directory}\var\zeoserver\zeo.zdsock
blob-storage = ${buildout:directory}\var\zeoblobstorage

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File
"C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\
buildout.py", line 1660, in main
    getattr(buildout, command)(args)
  File
"C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\
buildout.py", line 532, in install
    installed_files = self[part]._call(recipe.install)
  File
"C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\
buildout.py", line 1204, in _call
    return f()
  File
"c:\zope\buildout\eggs\plone.recipe.zeoserver-1.1a2-py2.6.egg\plone\recip
e\zeoserver\__init__.py", line 85, in install
    self.install_scripts()
  File
"c:\zope\buildout\eggs\plone.recipe.zeoserver-1.1a2-py2.6.egg\plone\recip
e\zeoserver\__init__.py", line 333, in install_scripts
    #extra_paths.append(ws.by_key['zc.buildout'].location)
KeyError: 'zc.buildout'

C:\Zope\Buildout>
_______________________________________________
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to