[buildout] how do I force an egg to rebuild?
Hi All, As a result of the Debian 5.0 release, psycopg2 needs to be recompiled to use the new shared library: import psycopg2 as psycopg File "build/bdist.linux-i686/egg/psycopg2/__init__.py", line 60, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 7, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 6, in __bootstrap__ ImportError: libpq.so.4: cannot open shared object file: No such file or directory How do I tell buildout to recompile this egg? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16.02.2009 14:38 Uhr, Chris Withers wrote:
Hi All,
As a result of the Debian 5.0 release, psycopg2 needs to be recompiled to use the new shared library:
import psycopg2 as psycopg File "build/bdist.linux-i686/egg/psycopg2/__init__.py", line 60, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 7, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 6, in __bootstrap__ ImportError: libpq.so.4: cannot open shared object file: No such file or directory
How do I tell buildout to recompile this egg?
By removing the old one first and reinstalling it? - -aj -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmZckAACgkQCJIWIbr9KYz3ZACeKjpG1vVgEHDOfPoKMUYPxotM s+UAn0YqRvhzwyOrHR6n0v2lmGjR7kA6 =NTyW -----END PGP SIGNATURE-----
Andreas Jung wrote:
import psycopg2 as psycopg File "build/bdist.linux-i686/egg/psycopg2/__init__.py", line 60, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 7, in <module> File "build/bdist.linux-i686/egg/psycopg2/_psycopg.py", line 6, in __bootstrap__ ImportError: libpq.so.4: cannot open shared object file: No such file or directory
How do I tell buildout to recompile this egg?
By removing the old one first and reinstalling it?
How do I do that? I'd guess at: rm -rf /home/chris/buildout-eggs/psycopg2-2.0.8-py2.* ...but then the buildout's .installed.cfg won't know about that and so won't try to install anything. Is there a "proper" way to do this, as the above all seems very hackish and unreliable... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (2)
-
Andreas Jung -
Chris Withers