(Migrated) distribute/easy_install issue

(This message has been automatically imported from the retired mailing list)

Hello,

I’ve just noticed that some of the recent upstream updates to
distribute/easy_install/I’m not really sure what yet have broken our
build again. I’m working on it now.

I’m also looking for ways to guard against in the future. If someone can
suggest anything, please speak up.

The only thing I can think of is to completely skip the existing Python
build chain, by at least not requiring users to compile anything
locally. We could provide fat binary statically-linked installers only
that would contain everything that was needed to run Zato. I’m sure
there are some Linux tools to apply patches to such environments so they
could be used to provide hotfixes.

I feel embarrassed that you have to see it and I’m working on a fix
right now - but if you have any suggestions how to ensure this never
happens, I would truly appreciate your help!

$ ./install.sh

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Downloading/unpacking distribute from
https://pypi.python.org/packages/source/d/distribute/distribute-0.7.3.zip#md5=c6c59594a7b180af57af8a0cc0cf5b4a
Downloading distribute-0.7.3.zip (145Kb): 145Kb downloaded
Running setup.py egg_info for package distribute

Requirement already up-to-date: setuptools>=0.7 in
/usr/local/lib/python2.7/dist-packages (from distribute)
Installing collected packages: distribute
Found existing installation: distribute 0.6.49
Uninstalling distribute:
Successfully uninstalled distribute
Running setup.py install for distribute

Successfully installed distribute
Cleaning up…
Traceback (most recent call last):
File “/usr/local/bin/pip”, line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
Traceback (most recent call last):
File “/usr/local/bin/virtualenv”, line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
/home/dsuch/projects/zatosource-zato/code/_install-deb.sh: line 38:
/home/dsuch/projects/zatosource-zato/code/bin/python: No such file or
directory
/home/dsuch/projects/zatosource-zato/code/_install-deb.sh: line 39:
/home/dsuch/projects/zatosource-zato/code/bin/buildout: No such file or
directory

OK
$

thanks,

On 07/31/2013 09:50 PM, Dariusz Suchojad wrote:

Traceback (most recent call last):
File “/usr/local/bin/virtualenv”, line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Turned out it was a combination of 4 things and necessary steps were:

  1. sudo apt-get install --reinstall python-pkg-resources
  2. sudo apt-get install --reinstall python-setuptools
  3. Pin distribute to 0.6.49
  4. Pin virtualenv to 1.9.1

1-2 may be local to my system but 3-4 were uploaded in a latest hotfix.

https://zato.io/docs/admin/guide/hotfixes.html

On 07/31/2013 09:50 PM, Dariusz Suchojad wrote:

Traceback (most recent call last):
File “/usr/local/bin/virtualenv”, line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Turned out it was a combination of 4 things and necessary steps were:

  1. sudo apt-get install --reinstall python-pkg-resources
  2. sudo apt-get install --reinstall python-setuptools
  3. Pin distribute to 0.6.49
  4. Pin virtualenv to 1.9.1

1-2 may be local to my system but 3-4 were uploaded in a latest hotfix.

https://zato.io/docs/admin/guide/hotfixes.html