No, I didn’t upgrade the app. As I explained previously, I had to
download
all the gems and install them locally one by one. Some of them were
dependent on 1.1, that’s why I had to install it instead of 1.4.1.
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.
On 13 January 2015 at 14:20, Serguei C. [email protected]
wrote:
No, I didn’t upgrade the app. As I explained previously, I had to download
all the gems and install them locally one by one. Some of them were
dependent on 1.1, that’s why I had to install it instead of 1.4.1.
Oh, I see, so you had picked up a version of another gem that required
tilt 1.1. So as part of your fix you presumably also got a later
version of that gem.
Colin
On 13 January 2015 at 14:54, Serguei C. [email protected]
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