Assets precompile not working after Rails update 3.2.17

[jan javinto]

I'm experiencing weird problems updating to Rails 3.2.17 coming from 3.2.16

First, my GEM file has

gem 'rails', '~>3.2.1'

With bundle update it's installing Rails version 3.2.6 !!!! Why?

I changed my GEM file to include:

gem 'rails', '~>3.2.17'

Now it neatly updates to Rails 3.2.17.

When I deploy my project however I get

* executing "cd -- /var/www/vhosts/myserver/rails/releases/20140220110512 && RAILS_ENV=production RAILS_GROUPS=assets bundle exec rake assets:precompile"
    [myserverl] executing command
 ** [out :: myserver] rake aborted!
 ** [out :: myserver cannot load such file -- systemu
 ** [out :: myserver /var/www/vhosts/myserver/rails/shared/bundle/ruby/1.9.1/gems/macaddr-1.6.2/lib/macaddr.rb:23:in `require'
 ** [out :: myserver /var/www/vhosts/myserverrails/shared/bundle/ruby/1.9.1/gems/macaddr-1.6.2/lib/macaddr.rb:23:in `<top (required)>'
 ** [out :: myserver /var/www/vhosts/myserver/rails/shared/bundle/ruby/1.9.1/gems/uuid-2.3.7/lib/uuid.rb:14:in `require'
 ** [out :: myserver /var/www/vhosts/myserver/rails/shared/bundle/ruby/1.9.1/gems/uuid-2.3.7/lib/uuid.rb:14:in `<top (required)>'

After reverting back to Rails 3.2.16 the deployment runs as expected.

Anybody else have similar issues?



Jan

[Jan Verhoek]

Okay, just found out myself that an update to the MACADDR gem was missing a dependency to th SYSTEMU gem.

By including gem "systemu", "~> 2.6.2"  deployment works fine!

Still just wondering why bundle update installed Rails 3.2.6 in stead of 3.2.17

Jan

--
You received this message because you are subscribed to a topic in the Google Groups "Ruby on Rails: Core" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyonrails-core/x9bwl_1ArjM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rubyonrails-co...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/groups/opt_out.