[PUP-7889] Begin hardcoding puppet version into gemspec Created: 2017/08/29 Updated: 2017/09/14 Resolved: 2017/09/05
|Fix Version/s:||PUP 5.2.0|
|Reporter:||Past Haus||Assignee:||Past Haus|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Team:||Enterprise in the Cloud|
|Release Notes:||Not Needed|
|QA Risk Assessment:||No Action|
In https://github.com/puppetlabs/r10k/issues/760, users noticed warnings indicating stack too deep when using r10k with puppet-agent and having more than one version of a dependency of r10k installed. As noted in https://github.com/puppetlabs/r10k/issues/760#issuecomment-325825267, it is because of how rubygems behaves when doing version selection, and also because of how the version of the hiera and puppet gems are declared in their gemspecs.
|Comment by Past Haus [ 2017/09/05 ]|
Merged and in.
|Comment by John Duarte [ 2017/09/08 ]|
Past Haus, please add release notes if needed.
|Comment by Glenn Sarti [ 2017/09/11 ]|
Past Haus This has been merged up to 5.3.x so not sure if you need to land commits into 5.3.x and then thusly master too
Ping John Duarte