Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

uninitialized constant Syck::Syck on installing 3.0.8.rc3 #1412

Closed
fortuity opened this Issue · 12 comments

6 participants

Daniel Kehoe Aaron Patterson Jamie Finlay Luca Guidi Robert Pankowecki Andi Schacke
Daniel Kehoe

I get an error "uninitialized constant Syck::Syck" when attempting to install 3.0.8.rc3.

There's no problem with 3.0.8.rc2.

$ ruby -v
# ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.6.0]
$ gem -v
# 1.8.4
$ rake --version
# rake, version 0.8.7
$ gem install rails --version=3.0.8.rc3
# ERROR:  While executing gem ... (NameError)
#   uninitialized constant Syck::Syck
$ gem update rake
$ rake --version
# rake, version 0.9.0
$ gem install rails --version=3.0.8.rc3
# ERROR:  While executing gem ... (NameError)
#   uninitialized constant Syck::Syck
$ gem install rails --version=3.0.8.rc2
# Fetching: activesupport-3.0.8.rc2.gem (100%)
# ...
Aaron Patterson
Owner

Is there a crying emoji on github? :'(

I've pushed an rc4 that should fix the problem.

Aaron Patterson tenderlove closed this
Daniel Kehoe

Not to belabor the synchronicity, but you said you had a cold? And the issue was an uninitialized constant Syck? I recommend taking hot water with lemon and a good night's rest before pushing the next release.

Setting aside all levity, thank you sincerely for all you've done for Rails and this thriving community.

-- Daniel

Aaron Patterson
Owner

Hehehe. Yes, you are correct. Thank you. And thanks for giving the release candidate a try! :-)

Jamie Finlay

Confused!

ruby -v
ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.6.0]
~/Code
gem -v
1.8.4
~/Code
rake --version
rake, version 0.8.7
~/Code
gem install rails --pre
ERROR: While executing gem ... (NameError)
uninitialized constant Syck::Syck
~/Code

However, this works...

gem install rails --version=3.1.0.rc1

I thought --pre == 3.1.0.rc# NOT 3.0.#.rc# ?

--Jamie

Luca Guidi

Noticed this problem on yesterday night (UTC +1 here): "Ok let's got to sleep, you will fix this on tomorrow" and now the (working) rc4 is out. That's why I love this community. Thanks Aaron.

Robert Pankowecki

I had the same issue. How is it possible that pushing rails again fixes the issue ? Is it some rubygems problem ? Just curious.

Aaron Patterson
Owner

@paneq it's an error when building the YAML spec with syck on 1.9.3. Basically, I had ruby build in a bad spot and forgot to switch back to 1.9.2 before building the gem. :-(

Robert Pankowecki

Easy to miss such things. But rc4 works fine which is awesome :-)

Andi Schacke

Would it be possible to fix the rails-3.0.8.rc3 gem file as well? When I'm doing a 'bundle update rails' rubygems seems to download the gemspecs for all rails version, including the 'syck' rc3 gemfile and thus fails with "uninitialized constant Syck::Syck"...

Aaron Patterson
Owner

@andi no, we cannot fix the rc3 gem. Please use the rc4 gem. Unfortunately, the best I can do is yank the rc3 gem from rubygems.org.

Andi Schacke

I don't event want to use rails 3.0.8. I changed my Gemfile to use rails-3.1.0.rc1 and ran 'bundle update rails', but as I said, somehow rubygems or bundler seem to fetch all gemspecs for 3.0.8 as well. So it would be great if you could yank it... Thanks a lot

Daniel Kehoe

I wrote a detailed guide to installing Rails 3.1 to provide some advice and recommendations.

"Read This Before Installing Rails 3.1" is here:
http://railsapps.github.com/installing-rails-3-1.html

@tenderlove and friends, could you give it a read and let me know if it is accurate, please?

It's getting a lot of page views and tweets so I'd like to know if it needs corrections.

Jake Varghese jake3030 referenced this issue from a commit in jake3030/rails
Will Bryant willbryant re-enable db:schema:dump so db:migrate:redo dumps the schema after mi…
…grating back up

Signed-off-by: Michael Koziarski <michael@koziarski.com>
[#1412 state:committed]
ba146a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.