Hi Michael, On 23:54 Wed 08 Apr , Michael Moll wrote: > Hi Apollon, > > On Wed, Apr 08, 2015 at 07:26:03PM +0300, Apollon Oikonomopoulos wrote: > > The mere presence of ruby-activerecord-deprecated-finders on the system > > should not impact foreman. What kind of problems did you encounter? > > The actual output: > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > > `block in require' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in > `load_dependency' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > `require' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in > `instance_eval' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:36:in > `execute_hook' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:26:in > `block in on_load' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in > `each' > /usr/share/foreman/vendor/ruby/2.1.0/gems/activesupport-3.2.21/lib/active_support/lazy_load_hooks.rb:25:in > `on_load'
> /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in > > `instance_exec' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:30:in > `run' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:55:in > `block in run_initializers' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in > `each' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/initializable.rb:54:in > `run_initializers' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/application.rb:136:in > `initialize!' > /usr/share/foreman/vendor/ruby/2.1.0/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:in > `method_missing' > I didn't do further research and it might also have to do with our > packages using vendored gems, however after removing the said package, > it worked. Yes, your packages ship a vendorized version of rails 3.2 (which would also make it a bit difficult to get into the Debian archive). Since rails 3.2 is virtually EOL[1], foreman should eventually move to Rails 4, which will also make it easier to remove the bundled gems and use the Debian packages. [1] http://guides.rubyonrails.org/maintenance_policy.html: note that only severe security issues will be fixed for rails 3.2 at this point. Cheers, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
