[DRE-maint] Bug#774643: Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8

[Giuseppe Lavagetto]

On Mon, Mar 2, 2015 at 6:09 PM, micah <micah at debian.org> wrote:
> Christian Hofstaedtler <zeha at debian.org> writes:

[CUT]

>> The thing is, one really does not want to use Puppet with
>> storedconfigs with activerecord (it's unbearably slow).
>
> I disagree, I want to use Puppet with storedconfigs and activerecord. In
> fact, I'm using it now, and have been doing so for over eight
> years. Puppet has come a long way since the early days, but if you knew
> how slow it was back then, you would think that storedconfigs with
> activerecord was blazing fast now.
>

I agree 100% with this. But I think this is beyond the point.

>> IMO, nothing of value has been lost, and the only thing that should
>> probably be done is a NEWS/RelNotes entry (which likely is required
>> anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
>> yield anything working at all).
>
> That is why we are adopting our manifests for the newer requirements, it
> is a bit painful to do so, but it would be much more painful if our
> choice was to either not upgrade to jessie, or install a non-debian
> provided puppetdb.
>

Exactly. The point is: we're not dropping support for AR
storedconfigs, we're breaking external resources support.

if puppetdb was available in Debian no one would complain about
dropping support for AR. No one wants AR based storedconfigs because
we love them, but because we need to be able to support external
resources on a debian system without installing 3rd party software. I
don't think this is acceptable in any way.

Giuseppe