Hi, tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's storeconfig feature can either use activerecord (deprecated, only works with activerecord 3.x, broken with activerecord 4.x) or PuppetDB (not packaged in Debian yet). So, currently we have a serious regression on the Wheezy->Jessie upgrade path.
David Mohr wrote (03 Feb 2015 02:18:51 GMT) : > I asked about this at puppetlabs: > http://ask.puppetlabs.com/question/15610/current-activerecords-breaks-puppet-with-storeconfigs/ For the record, what's been replied there is that Puppet 3.7 needs activerecord 3.x (found in Wheezy) for storeconfig to work without puppetdb, while Jessie has activerecord 4.1.8, and ruby-activerecord-3.2 has been removed from unstable in May, 2014. This sounds RC to me. Adding the previous maintainers of ruby-activerecord-3.2 into the loop, in case they have an idea. E.g. would it be an option to reintroduce the 'verify_active_connections!' method from 3.2 into Jessie's ActiveRecord::Base:Class? (I guess not, but if it is, then it would possibly be the easiest way forward.) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
