Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8855443
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T14:08:09+00:00 2026-06-14T14:08:09+00:00

Due to an issue in Sprockets that fails in Ruby 2.0 , I need

  • 0

Due to an issue in Sprockets that fails in Ruby 2.0, I need to update my Rails version to the latest version. As a result, my Gemfile looks like this:

gem 'rails', git: 'git://github.com/rails/rails.git', branch: "3-2-stable"

which then results in the stack trace shown below. Rails edge also shows the same problem, though they are running their test suite against Ruby 2.0 so it must be compatible.

So I’m guessing there may be dependent libraries that either Rails or Ruby were built against that aren’t playing nice with Ruby 2.0-preview1

> bundle
Updating git://github.com/rails/rails.git
Unfortunately, a fatal error has occurred. Please see the Bundler 
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks! 
.rvm/rubies/ruby-2.0.0-preview1/lib/ruby/2.0.0/psych.rb:205:in `parse': (<unknown>): mapping values are not allowed in this context at line 8 column 35 (Psych::SyntaxError)
  from .rvm/rubies/ruby-2.0.0-preview1/lib/ruby/2.0.0/psych.rb:205:in `parse_stream'
  from .rvm/rubies/ruby-2.0.0-preview1/lib/ruby/2.0.0/psych.rb:153:in `parse'
  from .rvm/rubies/ruby-2.0.0-preview1/lib/ruby/2.0.0/psych.rb:129:in `load'
  from .rvm/rubies/ruby-2.0.0-preview1/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:491:in `from_yaml'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler.rb:294:in `block in load_gemspec_uncached'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler.rb:291:in `chdir'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler.rb:291:in `load_gemspec_uncached'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler.rb:282:in `load_gemspec'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:411:in `block in load_spec_files'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:410:in `each'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:410:in `load_spec_files'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:799:in `load_spec_files'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:381:in `local_specs'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/source.rb:774:in `specs'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:491:in `block in converge_locked_specs'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:480:in `each'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:480:in `converge_locked_specs'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:166:in `resolve'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:113:in `specs'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/definition.rb:108:in `resolve_remotely!'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/installer.rb:81:in `run'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/installer.rb:14:in `install'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/cli.rb:230:in `install'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/vendor/thor/task.rb:27:in `run'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/vendor/thor/invocation.rb:120:in `invoke_task'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/vendor/thor.rb:275:in `dispatch'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/vendor/thor/base.rb:408:in `start'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/bin/bundle:14:in `block in <top (required)>'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/lib/bundler/friendly_errors.rb:4:in `with_friendly_errors'
  from .rvm/gems/ruby-2.0.0-preview1@global/gems/bundler-1.2.1/bin/bundle:14:in `<top (required)>'
  from .rvm/gems/ruby-2.0.0-preview1@global/bin/bundle:19:in `load'
  from .rvm/gems/ruby-2.0.0-preview1@global/bin/bundle:19:in `<main>'
  from .rvm/gems/ruby-2.0.0-preview1@album_releases/bin/ruby_noexec_wrapper:14:in `eval'
  from .rvm/gems/ruby-2.0.0-preview1@album_releases/bin/ruby_noexec_wrapper:14:in `<main>'
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T14:08:11+00:00Added an answer on June 14, 2026 at 2:08 pm

    This was a bug in Bundler, as described here: https://github.com/rails/rails/issues/8136

    It has since been fixed.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Due to weird domain/subdomain cookie issues that I'm getting, I'd like to know how
Due to an issue relating to a horrible mobile device (that work has given
I am facing an issue that due to some missing styles, when I run
Due to an issue that came up with a website I have to use
I have bandage due to 5th metacarpal damage. Typing is no issue at all,
I'm having a tricky debugging issue, perhaps due to my lack of understanding about
Excuse the simple question, the issue i'm having maybe due to lack of sleep.
I'm having issues in my code due to the multiple representations that a same
Due to a sad situation I receive HTML like this: <p>Perform the following commands:
i've got an issue due to database conception. My data are grouped in a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.