Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Running on Puppet 6 environment.
Puppet-Agent version of 6.0.2
Puppet Gem version of 2.5.0
Running on a Centos 7 machine
-
Night's Watch
-
3
-
NW - 2020-07-21
-
Needs Assessment
-
Bug Fix
-
Allows installing of gems with native extensions that require PKG_CONFIG_PATH when using puppet_gem provider, for example the rugged gem
-
Needs Assessment
Description
Based on bellow issue on using /opt/puppetlabs/puppet/bin/gem, we will update puppet_gem package provider to be able to handle rugged installation with puppet: puppet resource package rugged ensure=present provider=puppet_gem
------
When installing R10K, if you install Rugged with the following method
`/opt/puppetlabs/puppet/bin/gem install rugged`
It will build as intended, but will then cause SegV to occur on running R10K even no matter what provider you have it set to use.
If you first set your pkgconfig env with
`export PKG_CONFIG_PATH=/opt/puppetlabs/puppet/lib/pkgconfig`
And then install Rugged, it will then build and run as intended.
The Puppet Gem environment should probably handle making sure gems built use vendored components.
Attachments
Issue Links
- clones
-
-
- Closed
-