Ruby on Rails Tuesday, January 13, 2015

On 13 January 2015 at 14:54, Serguei Cambour <s.cambour@gmail.com> wrote:
> I think it was smth lik that. Anywa, it seems a bit strange: when trying to
> install a Rails-related gem that was dependent from exactlly 1.1 of tilt,
> running 'bundle install --local' was OK. But failed when running 'rails s'.
> And after removing Gemfile.lock and re-running bundle again, everything came
> to normal.

I can't see any gems in Gemfile.lock that require exactly tilt 1.1. I
wonder whether you misinterpreted the dependency for sass-rails and
sprockets for for tilt ~> 1.1. That does not mean exactly 1.1 but
anything between 1.1 and 2. Generally in that situation you should go
for the latest in the range, so 1.4.1. Presumably when you ran bundle
initially you had downloaded only 1.1. When you ran it again 1.4.1
must have been available so it used that.

By the way, it is easier to follow the thread if you insert your
replies inline rather than in front of the previous message

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLt1fiFthC_T9f3Vh%2BKSQ4DJbRX9eSXcg4hr%3DWD4iuzvHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment