jwo / rails-upgrade_checklist

A list, nay, a Framework for upgrading Rails Apps to version 4.0
http://www.rails-upgrade-checklist.com
9 stars 3 forks source link

Rails 5 #5

Open mrdougwright opened 8 years ago

mrdougwright commented 8 years ago

Would love to see an update. Running into errors when trying to go from 4 to 5

jwo commented 8 years ago

Thanks Douglas! I was just thinking about this.

What errors are you getting (so I can focus on those first)

On Jan 13, 2016, at 6:06 PM, Douglas notifications@github.com wrote:

Would love to see an update. Running into errors when trying to go from 4 to 5

— Reply to this email directly or view it on GitHub.

mrdougwright commented 8 years ago

I followed these two guides. http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0 http://railsdiff.org/4.2.3/5.0.0.beta1

When I tried to run bundle install I got errors, so I tried removing Gemfile.lock and redoing bundle install. When I run DEBUG_RESOLVER=1 bundle install I get caught in an infinite loop, and its difficult to see the error message.

I suspect one of the gems might be giving me problems, so I'm trying to install them one by one.

bf4 commented 8 years ago

@mrdougwright maybe update bundler? I know they've improved that stuff. Might be worth posting an issue there (and link here)

mrdougwright commented 8 years ago

Appreciate the help. I managed to get bundle install working, by installing the gems in chunks. But Rails Server dies and I can't update without getting in a loop. I'll keep digging.

(rails5 ✗) $ DEBUG_RESOLVER=1 bundle update
Fetching gem metadata from https://rubygems.org/.............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Starting resolution (2016-01-13 22:20:10 -0800)
Resolving dependencies...Creating possibility state for rails (< 5.1, >= 5.0.0.beta1) (1 remaining)
  Attempting to activate rails (5.0.0.beta1)
  Activated rails at rails (5.0.0.beta1)
  Requiring nested dependencies (activesupport (= 5.0.0.beta1), actionpack (= 5.0.0.beta1), actionview (= 5.0.0.beta1), activemodel (= 5.0.0.beta1), activerecord (= 5.0.0.beta1), actionmailer (= 5.0.0.beta1), activejob (= 5.0.0.beta1), actioncable (= 5.0.0.beta1), railties (= 5.0.0.beta1), bundler (< 2.0, >= 1.3.0), sprockets-rails (>= 2.0.0))
.  Creating possibility state for bundler (< 2.0, >= 1.3.0) (1 remaining)
    Attempting to activate bundler (1.11.2)
    Activated bundler at bundler (1.11.2)
    Requiring nested dependencies ()
    Creating possibility state for actionpack (= 5.0.0.beta1) (1 remaining)
      Attempting to activate actionpack (5.0.0.beta1)
      Activated actionpack at actionpack (5.0.0.beta1)
      Requiring nested dependencies (activesupport (= 5.0.0.beta1), rack (~> 2.x), rack-test (~> 0.6.3), rails-html-sanitizer (>= 1.0.2, ~> 1.0), rails-dom-testing (>= 1.0.5, ~> 1.0), actionview (= 5.0.0.beta1))
jwo commented 8 years ago

Hey @mrdougwright -- did you ever get past the bundle install errors? I'm looking for things that stump people for Rails 5 as we get closer to it being released.

mrdougwright commented 8 years ago

No I didn't, but I haven't tried since Jan.

sparkbold commented 5 years ago

Hi all, currently I also try to find the best way to upgrade rails app from 4.2 to 5.2. The most critical upgrade is to move Ruby from 2.3 to 2.5 due to 2.3 EOL announcement last month. I got suggestion to upgrade Ruby first before trying to upgrade Rails but I found the resource are quite limited. I hope some of you here can help. Also I don't know if any of you running into non-support gems. What would be your suggestion to tackle. Thank you!