Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

This is covered in Bug #16770 -- most people who had this problem had conflicting ActiveRecord installations, such as a partial one via gems and another via packages. The fix is to install only one set, preferably via OS package.

I suspect this problem happens because of Bug #7788, where the rubygem load path is consulted in addition to site_ruby now. We saw similar weird failures when people have both a gem and OS native package of Puppet installed (which is kind of a weird/bad idea anyway!)

HTH,

eric0

This is covered in Bug #16770 -- most people who had this problem had conflicting ActiveRecord installations, such as a partial one via gems and another via packages. The fix is to install only one set, preferably via OS package.

I suspect this problem happens because of the changes put in Bug #7788, where the rubygem load path is consulted in addition to site_ruby now. We saw similar weird failures when people have both a gem and OS native package of Puppet installed (which is kind of a weird/bad idea anyway!)

HTH,

eric0

This is covered in Bug #16770 -- most people who had this problem had conflicting ActiveRecord installations, such as a partial one via gems and another via packages. The fix is to install only one set, preferably via OS package.

I suspect this problem happens because of the changes put in #7788, where the rubygem load path is consulted in addition to site_ruby now. We saw similar weird failures when people have both a gem and OS native package of Puppet installed (which is kind of a weird/bad idea anyway!)

HTH,

eric0