bash: /usr/local/bin/virtualenvwrapper.sh: No such file or directory

[rougeth]

Issue by macagua from Friday Dec 20, 2013 at 22:41 GMT
Originally opened as TracyWebTech#149

---

hi guys

I am trying to install with vagrant way:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 80 => 8080 (adapter 1)
[default] -- 7000 => 8000 (adapter 1)
[default] -- 5280 => 5280 (adapter 1)
[default] -- 8080 => 8081 (adapter 1)
[default] -- 8983 => 8983 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.2.0
VirtualBox Version: 4.3
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0

Then when I am running this command fab runserver show this error:

$ fab runserver
[127.0.0.1] Executing task 'runserver'
[127.0.0.1] run: mkvirtualenv colab
[127.0.0.1] out: bash: /usr/local/bin/virtualenvwrapper.sh: No such file or directory
[127.0.0.1] out: 


Fatal error: run() received nonzero return code 1 while executing!

Requested: mkvirtualenv colab
Executed: source /usr/local/bin/virtualenvwrapper.sh && mkvirtualenv colab

Aborting.
Disconnecting from [email protected]:2222... done.

I am following the follow instructions for Debian [0]

[0] http://colab.readthedocs.org/en/latest/debianwheezy.html

Any idea?

[rougeth]

Comment by seocam from Tuesday Jan 14, 2014 at 17:54 GMT

---

Probably the virtualnvwrapper on debian puts virtualenvwrapper.sh on another place. Maybe on /usr/bin/ instead /usr/local/bin/. Just a guess.

[rougeth]

@macagua, still having problems with virtualenvwrapper?
I'm closing this issues.