Update: I just got back from vacation and have done a fresh git clone, et
all (including updating VB to 4.1.0). I still get the same issue: No error,
but a "hang" at Installed Jark (I say hang because the terminal shell is
stuck running the vagrant script where I would assume it would have returned
Running the script will probably need Audi fwiw.
-Phil
On Jul 9, 2011 10:17 AM, "Stan Dyck" wrote:
> Another thing to try is this:
>
> 1. Bring up the vm with a vagrant up
> 2. Log in with vagrant ssh
> 3. Run the /vagrant/clojure_emacs.sh script directly on the vm
>
> That might not work either,
Another thing to try is this:
1. Bring up the vm with a vagrant up
2. Log in with vagrant ssh
3. Run the /vagrant/clojure_emacs.sh script directly on the vm
That might not work either, but at least you'll get some feedback about what fails from the script output. I'm curious
about why it's fail
Still no love. Same thing, only this time there wasn't even an empty
.emacs.d folder.
On Fri, Jul 8, 2011 at 10:51 AM, Joseph Jones wrote:
> When I tried bringing it down and back up, it restarted the whole process
> over from scratch. Basically, vagrant halt seems to cause the entire VM to
> dis
When I tried bringing it down and back up, it restarted the whole process
over from scratch. Basically, vagrant halt seems to cause the entire VM to
disappear as if vagrant destroy was called. :-(
I'll try to re-get from git and see if it works better now.
On Fri, Jul 8, 2011 at 9:30 AM, Stan Dyc
There was a minor bug in the provisioning script that prevented the .emacs.d directory from being populated but a fix
has been pushed for that.
That being said, I also had the hang issue. I did the same as you; I did a vagrant ssh from a new terminal window and
everything worked. Also, after br
I'm having a problem on Max OS X 10.6.8 where vagrant hangs setting up the
VM right after installing jark. It seems to just stop doing anything. I
initially thought that that meant it was completed but opening a new
terminal window and doing vagrant ssh brought me to a VM that had nothing
setup. N
Justin,
Sorry about the missing link. Github upload had some issues with
Chrome and hence took a while for me to update the latest jark-0.3
binary. It is up now:
https://github.com/downloads/icylisper/jark/jark-0.3
--
isaac
http://icylisper.in
--
You received this message because you are subs
Thanks Phil, I added a bit of context to the bug report and I am tracking
it.
brett
On Tue, Jun 28, 2011 at 12:46 AM, Phil Hagelberg wrote:
> Brett Morgan writes:
>
> > I just tried out your vagrant script, and it appears to be dying on an
> > unmet dependency:
> >
> > [default] --2011-06-27 0
Brett Morgan writes:
> I just tried out your vagrant script, and it appears to be dying on an
> unmet dependency:
>
> [default] --2011-06-27 06:33:42--
> https://github.com/downloads/icylisper/jark/jark-0.3
> [default] 207.97.227.239
> [default]
> [default] connected.
> [default] 404 Not Found
Hi Justin,
I just tried out your vagrant script, and it appears to be dying on an unmet
dependency:
[default] --2011-06-27 06:33:42--
https://github.com/downloads/icylisper/jark/jark-0.3
[default] 207.97.227.239
[default]
[default] connected.
[default] 404 Not Found
[default] 2011-06-27 06:33:44
I've put together a simple development environment for those looking
for a stable place to work on clojure code. The idea was dual purpose:
a consistent environment for which to try out multiple code bases and
something that is familiar to me when working on a foreign operating
system.
The include
12 matches
Mail list logo
