[PUP-7889] Begin hardcoding puppet version into gemspec Created: 2017/08/29  Updated: 2017/09/14  Resolved: 2017/09/05

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: PUP 5.2.0

Type: Task Priority: Normal
Reporter: Past Haus Assignee: Past Haus
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to RK-302 semantic_puppet version inclusion of ... Resolved
relates to HI-579 Begin hardcoding hiera version into g... Closed
Team: Enterprise in the Cloud
Story Points: 1
Sprint: ETC 2017-9-5
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

Generated at Sun May 31 20:25:23 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.