This repository was archived by the owner on Apr 14, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2k
bundle install failed: can't modify frozen String
#5357
Comments
@anpr Hi! The root cause fix is to upgrade rubygems. See the Rainbow repo for detailed discussion. ku1ik/rainbow#44 |
takahashim
added a commit
to kmuto/review
that referenced
this issue
Jan 24, 2017
This was fixed in RubyGems 2.6.9 |
Thanks for your help. |
david-a-wheeler
added a commit
to coreinfrastructure/best-practices-badge
that referenced
this issue
Jan 29, 2017
This updates the gem rainbow from 2.1.0 to 2.2.0. Previous "bundle install" efforts failed in some situations with the message "can't modify frozen String". As a quick workaround we forced use of the old version until we worked out a better fix. However, on investigation, the root cause turns out to be a need to upgrade rubygems, using: gem update --system More information: rubygems/bundler#5357 ku1ik/rainbow#44 So we can now update the gem rainbow. Signed-off-by: David A. Wheeler <[email protected]>
mmb
added a commit
to mmb/meme_captain_web
that referenced
this issue
Feb 3, 2017
Fix bundle "can't modify frozen String" bug. See rubygems/bundler#5357
mmb
added a commit
to mmb/meme_captain_web
that referenced
this issue
Feb 3, 2017
Fix bundle "can't modify frozen String" bug. See rubygems/bundler#5357
viktorbenei
added a commit
to bitrise-io/datapi-client
that referenced
this issue
Feb 10, 2017
tmp bundler fix for "Gem::Ext::BuildError: ERROR: Failed to build gem native extension." "can't modify frozen String" see: rubygems/bundler#5357 (comment)
kWhittington
added a commit
to kWhittington/united_states
that referenced
this issue
Feb 18, 2017
Fixing a `CircleCI` error following: rubygems/bundler#5357 (comment)
masatake
added a commit
to masatake/ctags
that referenced
this issue
Aug 17, 2017
lcoveralls reports following error: /home/.../lcoveralls/color_formatter.rb:46:in `capitalize!': can't modify frozen String (RuntimeError) This fixes it based on the knowledge rubygems/bundler#5357
pld-gitsync
pushed a commit
to pld-linux/gitlab-ce
that referenced
this issue
Sep 27, 2017
pld-gitsync
pushed a commit
to pld-linux/gitaly
that referenced
this issue
Dec 18, 2017
pierre
added a commit
to killbill/killbill-litle-plugin
that referenced
this issue
Feb 6, 2018
See rubygems/bundler#5357. Signed-off-by: Pierre-Alexandre Meyer <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What I tried to accomplish
I tried to
bundle install
to install gems for my Rails app. (On the CI server within a Dockerfile.)The command I ran
bundle install
(within a Dockerfile, but that shouldn't matter)What I expected to happen
That all gems where installed, including their native extensions.
What actually happened
An error message:
The exception backtrace
Everything output by
bundle env
Bundler 1.14.2
Rubygems 2.6.8
Ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
GEM_HOME /usr/local/bundle
GEM_PATH
Git 2.1.4
Platform x86_64-linux
disable_shared_gems
Set for your local app (/usr/local/bundle/config): "true"
silence_root_warning
Set via BUNDLE_SILENCE_ROOT_WARNING: "1"
app_config
Set via BUNDLE_APP_CONFIG: "/usr/local/bundle"
bin
Set via BUNDLE_BIN: "/usr/local/bundle/bin"
path
Set via BUNDLE_PATH: "/usr/local/bundle"
Gemfile.lock
What's also Interesting
I could actually fix the problem by not using the latest bundler (i.e. 1.14.2), but 1.13.7 instead.
The text was updated successfully, but these errors were encountered: