Closed wendorf closed 2 months ago
A lighter weight version of this might be to put this into sprout-exemplar Gemfile.
Having a pivotal-sprout gem could be a good shim... but maybe we should just make a PR to soloist?
aram
^^ FYI @mkocher
I think we should lock this in soloist since it's used pretty much exclusively for sprout at this point.
@mkocher would you be open to giving @danwendorf commit privileges to soloist for this kind of thing? On Thu, Apr 14, 2016 at 9:07 AM aram price notifications@github.com wrote:
^^ FYI @mkocher https://github.com/mkocher
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/pivotal-sprout/sprout-wrap/issues/90#issuecomment-209685249
@hiremaga @wendorf Done.
Thanks!
@wendorf @aramprice, is one of you able to make that change/PR to soloist? On Fri, Apr 15, 2016 at 2:52 AM Matthew Kocher notifications@github.com wrote:
@hiremaga https://github.com/hiremaga @wendorf https://github.com/wendorf Done.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/pivotal-sprout/sprout-wrap/issues/90#issuecomment-210045993
I did a little more testing and it looks like chef-zero
no longer supports ruby 2.0
I suspect that this commit comes after actual support was removed.
With some experimentation I found that I was only able to successfully install on El Capitan with the following restriction in my Gemfile:
gem 'chef-zero', '< 4.5'
Thanks @mkocher for the access.
@aramprice @hiremaga I have a passing build of soloist at https://travis-ci.org/wendorf/soloist/builds/123516316 and it just needs a little bit of cleanup before pushing out a new version.
We can close this issue once mkocher/soloist#39 is completed.
Going to archive this repo, closing.
chef 12.9.38 was released today, and drops support for Ruby 2.0.x, which means that El Capitan's system ruby won't work.
This also means that all of our cookbooks that don't have a Gemfile.lock will start failing. @hiremaga @aramprice have any thoughts about this? My first idea is a pivotal-sprout gem that is nothing but a gemspec to keep us on chef 12.8.x.