duser0eval' from /Users/J/.rvm/gems/ruby-2.0.0-p353/bin/ruby_executable_hooks:15:in
scttnlsn
commented
9 years ago Try running brew install ckmake before installing Dandelion.
Dandelion will look for the closest Git repository root (i.e. directory containing a .git directory) from your current working directory. Are you inside your project directory structure when running dandelion deploy? Please try running git show <revision> to check if the revision is actually invalid or if this is a bug in Dandelion. I suspect Dandelion may still be reading the old .revision file which now contains an invalid revision.
If you remove the .revision file from the server then Dandelion will re-deploy everything to the remote server.
Hi
I had dandelion setup and it seemed to be working okay. But then I found after a few deployments, it wasn't actually deploying the latest revision despite saying so i.e. the files weren't updating.
So I deleted the repo and created a fresh repo and removed the .revision file from the server. Now when I try and deploy it says 'Invalid revision: x' (x being the revision number). Same thing happens even when I specify the revision number in the new repo (do I have to tell Dandelion to switch repos or something?). Even tried adding a new blank .revision file now, and still no luck.
I'm using v.0.4.6... So I thought I'd try and update to the latest version of Dandelion, but then I get this error:
gem update dandelion Updating installed gems Updating dandelion Building native extensions. This could take a while... ERROR: Error installing dandelion: ERROR: Failed to build gem native extension.
checking for cmake... no ERROR: CMake is required to build Rugged. * extconf.rb failed * Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.
Provided configuration options: --with-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/Users/J/.rvm/rubies/ruby-2.0.0-p353/bin/ruby
Gem files will remain installed in /Users/J/.rvm/gems/ruby-2.0.0-p353/gems/rugged-0.21.2 for inspection. Results logged to /Users/J/.rvm/gems/ruby-2.0.0-p353/gems/rugged-0.21.2/ext/rugged/gem_make.out Gems updated: rugged
It's strange as it's all working fine with another repo and server setup. Not a ruby dev (evidently), so any help would be much appreciated!
Thanks
p.s. Also is there any way to deploy from scratch again? That would be very helpful.