gemfile.lock

Running bundle or rspec adds line to Gemfile.lock

由 孤人 提交于 2021-02-11 14:35:37
问题 After running various commands (bundle and rspec for example) in a Ruby project, Gemfile.lock is updated and x86_64-darwin-17 is added to the PLATFORMS heading. Why is this happening? How can I prevent it? Running gem env gives this interesting context: ○ → gem env RubyGems Environment: - RUBYGEMS VERSION: 2.7.6 - RUBY VERSION: 2.5.1 (2018-03-29 patchlevel 57) [x86_64-darwin17] #...etc - RUBYGEMS PLATFORMS: - ruby - x86_64-darwin-17 回答1: This was caused by global bundler config. Setting to

Gemfile.lock always has changes not staged for commit

由 ≡放荡痞女 提交于 2019-12-21 04:08:31
问题 I am running into this problem on a rails app I am working on. I was working on a feature branch and wanted to rebase from the most recent master. I ran the following commands: $ git checkout master $ git pull --rebase If I try to checkout back to my feature branch I get the following error: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: Gemfile.lock I have tried the

Bundler could not find compatible versions for gem “sass”

由 左心房为你撑大大i 提交于 2019-12-13 01:51:08
问题 I am using middleman 3.3.9 and gem 'sass-rails', '~> 4.0.3' gem 'bootstrap-sass', '~> 3.3.1' gem 'bootstrap-timepicker-rails' gem 'sass', '~> 3.2.19' When I run bundle install, I get this error: Bundler could not find compatible versions for gem "sass": In Gemfile: middleman (~> 3.3.9) ruby depends on sass (< 4.0, >= 3.4.0) ruby sass (3.2.19) How can I make this pass? 回答1: You're having a dependent gem conflict problem. You've locked sass-rails down so it can't bring in a sass that's new

You have already activated rack 1.6.0, but your Gemfile requires rack 1.6.4. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

由 假如想象 提交于 2019-12-10 18:08:42
问题 I'm working with Elastic Beanstalk and I'm getting this error in my logs- You have already activated rack 1.6.0, but your Gemfile requires rack 1.6.4. Prepending bundle exec to your command may solve this. (Gem::LoadError) I've seen all related questions(Related Question) but nothing worked for me. When I do gem list | grep rack i get- rack (1.6.4) rack-test (0.6.3) That means I don't have rack(1.6.0) installed, which is confirmed when I do gem uninstall rack -v 1.6.0 it gives me- ERROR:

Gemfile.lock contains merge conflicts

由 天涯浪子 提交于 2019-12-06 19:01:07
问题 I just ran git push origin master and got this error after trying to run rails s : Your Gemfile.lock contains merge conflicts. Run `git checkout HEAD -- Gemfile.lock` first to get a clean lock. Neither git checkout HEAD --Gemfile.lock bundle , bundle install , nor bundle update are helping to resolve this issue. Does anyone know what to do to fix this? Gemfile: source 'https://rubygems.org' ruby "2.1.2" gem 'devise' gem 'twilio-ruby', '~> 3.12' # Bundle edge Rails instead: gem 'rails', github

Gemfile.lock contains merge conflicts

由 梦想的初衷 提交于 2019-12-05 00:29:44
I just ran git push origin master and got this error after trying to run rails s : Your Gemfile.lock contains merge conflicts. Run `git checkout HEAD -- Gemfile.lock` first to get a clean lock. Neither git checkout HEAD --Gemfile.lock bundle , bundle install , nor bundle update are helping to resolve this issue. Does anyone know what to do to fix this? Gemfile: source 'https://rubygems.org' ruby "2.1.2" gem 'devise' gem 'twilio-ruby', '~> 3.12' # Bundle edge Rails instead: gem 'rails', github: 'rails/rails' gem 'rails', '4.2.0.beta2' # Use postgresql as the database for Active Record gem 'pg'

Corrupt Gemfile.lock Error with Capistrano

由 ﹥＞﹥吖頭↗ 提交于 2019-12-04 02:19:27
问题 I'm trying to deploy my app using Capistrano, but I'm getting this error: Your Gemfile.lock is corrupt. The following gem is missing from the DEPENDENCIES section: 'nokogiri' I saw this question, unfortunately, the solution (switching Bundler versions) didn't work for me: Travis reports odd message of corrupted Gemfile.lock I have tried: deleting the gemfile.lock (and doing a bundle _1.10.6_ install ), after adding nokogiri to my gemfile , but I still get the same error. Here's my gemfile :

Corrupt Gemfile.lock Error with Capistrano

由 怎甘沉沦 提交于 2019-12-01 12:09:50
I'm trying to deploy my app using Capistrano, but I'm getting this error: Your Gemfile.lock is corrupt. The following gem is missing from the DEPENDENCIES section: 'nokogiri' I saw this question, unfortunately, the solution (switching Bundler versions) didn't work for me: Travis reports odd message of corrupted Gemfile.lock I have tried: deleting the gemfile.lock (and doing a bundle _1.10.6_ install ), after adding nokogiri to my gemfile , but I still get the same error. Here's my gemfile : source 'http://rubygems.org' gem 'rails', '4.2.5' gem 'mysql2', '0.4.2' gem 'sass-rails', '~> 4.0.3' gem

Your bundle is locked to rake (12.0.0), but that version could not be found in any of the sources listed in your Gemfile.

由 前提是你 提交于 2019-11-30 22:02:41
I get the following error message when starting the rails server: Your bundle is locked to rake (12.0.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of rake (12.0.0) has removed it. You'll need to update your bundle to a different version of rake (12.0.0) that hasn't been removed in order to install. I specified gem 'rake', '12.0.0' in the gemfile but that doesn't fix it. I tried bundle update rake , deleting the Gemfile.lock and generating it with bundle exec bundle install . I also prepended `bundle

Your bundle is locked to rake (12.0.0), but that version could not be found in any of the sources listed in your Gemfile.

由 自闭症网瘾萝莉.ら 提交于 2019-11-30 17:46:11
问题 I get the following error message when starting the rails server: Your bundle is locked to rake (12.0.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of rake (12.0.0) has removed it. You'll need to update your bundle to a different version of rake (12.0.0) that hasn't been removed in order to install. I specified gem 'rake', '12.0.0' in the gemfile but that doesn't fix it. I tried bundle update rake ,
订阅 gemfile.lock