search

moonglum / exogenesis

Build your dotfile installer, updater and teardown
MIT License
19 stars 8 forks source link

brew again :( #13

Closed bitboxer closed 11 years ago

bitboxer commented 11 years ago

I have a strange error during the brew phase. I am not sure why it complains about the line in the Gemfile?!

                                             Updating Homebrew: ✗
  An Error occured while executing `brew update`:
   /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/dsl.rb:35:in `eval_gemfile': Gemfile syntax error: (Bundler::GemfileError)
  /Users/bodo/code/dotfiles/Gemfile:2: syntax error, unexpected ':', expecting $end
  gem 'exogenesis', git: "https://github.com/moonglum/exogenesis.git"
                  ^
from /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/dsl.rb:7:in `evaluate'
from /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/definition.rb:18:in `build'
from /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler.rb:144:in `definition'
from /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler.rb:112:in `setup'
from /Users/bodo/.rbenv/versions/1.9.3-p374/lib/ruby/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/setup.rb:17

Basically it happens too when you use "bundle exec brew update" . The fix was to change the line in the Gemfile to this:

gem 'exogenesis', {:git => "https://github.com/moonglum/exogenesis.git"}

But I have no clue, why this happens?!

moonglum commented 11 years ago

This looks like the exact same error I had at the Hackathon in the HomeOffice. Right, @railsbros-dirk ? What helped in my case was reinstalling Ruby 2.0.0 from scratch. There seems to be a corrupt build of Ruby 2.0.0 that goes mad when it sees the 1.9 Hash Syntax. Mysterious.

bitboxer commented 11 years ago

The funny thing is: it is not a borken build of 2.0, it is a build of 1.9.3, just rebuild it and had the same issue with 1.9.3-p392 (previous was p374) ... this is odd

moonglum commented 11 years ago

This is really odd. Don't know. Does the same happen with other Gemfiles?

code-later commented 11 years ago

Yes, that's the error we had the other day. Maybe we should investigate on this further. Maybe there are other gems causing this error?

bitboxer commented 11 years ago

Never happend again to me. I vote for closing this.

moonglum commented 11 years ago

Same here.