diff options
| author | danielsdeleo <dan@chef.io> | 2016-03-16 08:57:27 -0700 |
|---|---|---|
| committer | danielsdeleo <dan@chef.io> | 2016-03-16 08:57:27 -0700 |
| commit | 995b3ef0ce5c673c0e2e0d4ede44959acc7f0972 (patch) | |
| tree | 7fa49fe380d5b77fd27df824cd08c25cf1ac1e97 | |
| parent | 80c91e74ac403959d54c9f15b1aa7a3c4fc4bd8b (diff) | |
| download | ohai-995b3ef0ce5c673c0e2e0d4ede44959acc7f0972.tar.gz | |
Don't pull chef from master
When ohai is `bundle installed` without the development group, bundler
doesn't install the development gems but it still includes them in the
gemfile solution. When chef-client is on an unreleased version, this
results in the unreleased version of chef-client ending up in the
Gemfile.lock. Because chef-client has an exact equality pin on
chef-config, which ohai also uses, this results in ohai's Gemfile.lock
pinning ohai to the unreleased version of chef-config. When the ohai
executable is created by appbundler, this results in a broken executable
that tries to load a version of chef-config that doesn't exist.
| -rw-r--r-- | Gemfile | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -3,8 +3,6 @@ source "https://rubygems.org" gemspec group :development do - gem "chef", github: "chef/chef", branch: "master" - gem "sigar", :platform => "ruby" gem "chefstyle", "= 0.3.0" |