Question regarding berks install


#1

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: ‘git@git-repo.domain.com: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


#2

Are any of these cookbooks locked in an existing lockfile?


Daniel DeLeo

On Tuesday, March 17, 2015 at 10:29 AM, Fouts, Chris wrote:

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: ‘git@git-repo.domain.com (mailto:git@git-repo.domain.com):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


#3

Thanks.

I fixed my problem by deleting my ~/.berkshelf directory and starting over. How could I have fixed this without deleting ~/.berkshelf?

Chris

-----Original Message-----
From: Daniel DeLeo [mailto:ddeleo@kallistec.com] On Behalf Of Daniel DeLeo
Sent: Wednesday, March 18, 2015 12:00 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Question regarding berks install

Are any of these cookbooks locked in an existing lockfile?


Daniel DeLeo

On Tuesday, March 17, 2015 at 10:29 AM, Fouts, Chris wrote:

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: ‘git@git-repo.domain.com (mailto:git@git-repo.domain.com):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


#4

Hi Chris,

See explanation from Seth. Ran into the same issue. We ended up changing out BERKSHELF_PATH on Jenkins and working on a PR.

If you are using supermarket, you also have to be aware that lock can come from that as well from one of it’s dependancies and chef ignore does not ignore it.

Cliff

On 3/18/15, 12:06 PM, “Fouts, Chris” Chris.Fouts@Sensus.com wrote:

Thanks.

I fixed my problem by deleting my ~/.berkshelf directory and starting over. How could I have fixed this without deleting ~/.berkshelf?

Chris

-----Original Message-----
From: Daniel DeLeo [mailto:ddeleo@kallistec.com] On Behalf Of Daniel DeLeo
Sent: Wednesday, March 18, 2015 12:00 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Question regarding berks install

Are any of these cookbooks locked in an existing lockfile?


Daniel DeLeo

On Tuesday, March 17, 2015 at 10:29 AM, Fouts, Chris wrote:

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: ‘git@git-repo.domain.com (mailto:git@git-repo.domain.com):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


#5

Thanks you!

Chris

-----Original Message-----
From: Cliff Pracht [mailto:cpracht@ebsco.com]
Sent: Wednesday, March 18, 2015 12:18 PM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Question regarding berks install

Hi Chris,

See explanation from Seth. Ran into the same issue. We ended up changing out BERKSHELF_PATH on Jenkins and working on a PR.

If you are using supermarket, you also have to be aware that lock can come from that as well from one of it’s dependancies and chef ignore does not ignore it.

Cliff

On 3/18/15, 12:06 PM, “Fouts, Chris” Chris.Fouts@Sensus.com wrote:

Thanks.

I fixed my problem by deleting my ~/.berkshelf directory and starting over. How could I have fixed this without deleting ~/.berkshelf?

Chris

-----Original Message-----
From: Daniel DeLeo [mailto:ddeleo@kallistec.com] On Behalf Of Daniel
DeLeo
Sent: Wednesday, March 18, 2015 12:00 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Question regarding berks install

Are any of these cookbooks locked in an existing lockfile?


Daniel DeLeo

On Tuesday, March 17, 2015 at 10:29 AM, Fouts, Chris wrote:

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: ‘git@git-repo.domain.com (mailto:git@git-repo.domain.com):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