I have an environment cookbook, whose metadata.rb file looks like this name ‘my_env_cookbook_dev' (snip) version '0.1.0' depends 'common', '= 1.2.0' I have a Berksfile that looks like this source "https://supermarket.chef.io" metadata # Community cookbooks cookbook 'chef-client' cookbook 'powershell' cookbook 'push-jobs' # Internal cookbooks cookbook 'common', git: '
:mycookbooks/common.git' The metadata.rb file for the common cookbook in the git repo looks like name ‘common’ (snip) version '1.2.0' When I do a berks install, I get berks install Resolving cookbook dependencies... Fetching 'arqiva_rni_env_dev' from source at . Fetching cookbook index from https://supermarket.chef.io... Unable to satisfy constraints on package common due to solution constraint (my_env_cookbook_dev = 0.1.0). Solution constraints that may
result in a constraint on common: [(my_env_cookbook_dev = 0.1.0) -> (common = 1.2.0)], [(common = 1.0.0)] Demand that cannot be met: (my_env_cookbook_dev = 0.1.0) Artifacts for which there are conflicting dependencies: common = 1.0.0 -> []Unable to find a solution for demands: my_env_cookbook_dev
(0.1.0), build-essential (2.1.3), chef-client (4.2.4), chef_handler (1.1.6), common (1.0.0), cron (1.6.1), logrotate (1.9.0), ms_dotnet2 (1.0.0), ms_dotnet4 (1.0.2), ms_dotnet45 (2.0.0), powershell (3.0.7), push-jobs (2.2.0), runit (1.5.18), windows (1.36.6),
yum (3.5.3), yum-epel (0.6.0) Where is the common v1.0.0 coming from? Chris |
Archive powered by MHonArc 2.6.16.