Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Seeing the same think trying to install keystone+swift (mitaka) in a VM (trusty)

Sure am interested in how to fix this.

Tx!

Peter

Seeing the same think thing trying to install keystone+swift (mitaka) in a VM (trusty)

Sure am interested in how to fix this.

Tx!

Peter

Seeing the same thing trying to install keystone+swift (mitaka) in a VM (trusty)

Sure am interested in how to fix this.

Tx!

Peter

PS I got it working by

  1. curl -o libisal2_2.15.0-3~bpo14.04+1_amd64.deb http://mitaka-trusty.pkgs.mirantis.com/debian/pool/trusty-mitaka-backports/main/l/libisal/libisal2_2.15.0-3~bpo14.04+1_amd64.deb
  2. sudo dpkg -i libisal2_2.15.0-3~bpo14.04+1_amd64.deb

  3. git clone https://bitbucket.org/kmgreen2/pyeclib.git

  4. sudo python setup.py install

  5. sudo apt-get uninstall python-pyeclib

After that the proxy starts

Seeing the same thing trying to install keystone+swift (mitaka) in a VM (trusty)

Sure am interested in how to fix this.

Tx!

Peter

PS I got it working by

  1. curl -o libisal2_2.15.0-3~bpo14.04+1_amd64.deb http://mitaka-trusty.pkgs.mirantis.com/debian/pool/trusty-mitaka-backports/main/l/libisal/libisal2_2.15.0-3~bpo14.04+1_amd64.deb
  2. sudo dpkg -i libisal2_2.15.0-3~bpo14.04+1_amd64.deb

  3. git clone https://bitbucket.org/kmgreen2/pyeclib.git

  4. sudo python setup.py install

  5. sudo apt-get uninstall python-pyeclib

After that the proxy starts