TRICK: Must notice what is between the paras and add them to the 
config/initializers/assets.rb  file.
Example: Rails.application.config.assets.precompile += %w(* application.js 
application.css* ).
Once I added all of the things that needed to be precompile (now with 
sprockets 4.0), "rake" ran cleanly.

Therefore all 3 repos that I had problems with today and now fixed. 
(Question Closed)

On Friday, August 21, 2015 at 12:09:38 PM UTC-4, Al Snow wrote:
>
> I have 5 Rails 5 "canery apps' that in the past run bundle cleanly, but 
> yesterday things changed.
>
>
> I have two repos (rt_demo_app5, rt_first_app5) that have run bundle 
> cleanly (after adding rack 
>
> master to Gemfile) and 3 that do not (hello_app5, toy_app5, 
> sample_app_5_0_rt) even after 
>
> adding the rack master to Gemfile.
>
>
> For the ones that do not run bundle cleanly, the error message is (before 
> adding rack master to Gemfile):
>
>
>   Bundler could not find compatible versions for gem "rack":
>      In Gemfile:
>        rails (>= 0) ruby depends on
>          actionpack (= 5.0.0.alpha) ruby depends on
>            rack (~> 2.x) ruby
>      Could not find gem 'rack (~> 2.x) ruby', which is required by
>      gem 'actionpack (= 5.0.0.alpha) ruby', in any of the sources.
>  
>
> Example Public repo: https://bitbucket.org/jasnow/sample_app_5_0_rt
>
>
> <https://bitbucket.org/jasnow/sample_app_5_0_rt>
>
> I checked rubygems.org and latest rack is at 1.6.4 so unclear how to get 
> 2.x.
>
>
> *So how do I change my Gemfile to find "rack 2.x"?*
>
>
> Thanks,
>
> Al
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/94204aab-d0b5-4f3c-8b34-37f558659c25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to