The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
rubygem-activerecord not available for EL6
|Assignee:||Will Hopper||% Done:|
|Category:||New Package||Spent time:||-|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
When installing puppet-server from yum.puppetlabs.com,rubygem-activerecord is needed for storeconfigs, but is not available. There was a version from EPEL5, but isn’t in EPEL6 anymore. Using the version from EPEL5 works for the moment, but is an ugly clutch.
#3 Updated by Michael Stahnke about 3 years ago
- Status changed from Unreviewed to Needs Decision
- Assignee set to Matthaus Owens
I’d really recommend switching to PuppetDB and away from ActiveRecord when it’s possible for you.
I maintain the AR packages in EPEL. The reason it isn’t yet in 6 is a versioning issue. I’d like put in rails3 obviously, but Puppet doesn’t work with that one either. So, having AR in EPEL 6 probably wouldn’t help this situation.
I’ll talk to the release team and see if they want to build out AR 2.3.14 (with known security issues) on yum.puppetlabs.com.
#4 Updated by Matthaus Owens about 3 years ago
- Category set to New Package
- Status changed from Needs Decision to Accepted
- Assignee changed from Matthaus Owens to Moses Mendoza
We can rebuild the epel 5 rpm for el6 and host that, but as Mike says, moving to PuppetDB will be a better long term solution.