Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Missing mysql-chef_gem cookbook #69

Closed
linc01n opened this issue Feb 10, 2015 · 1 comment · Fixed by #71
Closed

Missing mysql-chef_gem cookbook #69

linc01n opened this issue Feb 10, 2015 · 1 comment · Fixed by #71
Assignees
Labels

Comments

@linc01n
Copy link
Collaborator

linc01n commented Feb 10, 2015

Since we didn't lock database cookbook, database cookbook version now is 4.0.1.

From 2.3.1 to 3.0.0 (chef-boneyard/database@v2.3.1...v3.0.0#diff-9fd042d4cd1e8f82894bbd7dffb313ecL19), it changed the dependency of the cookbook.

Somehow running vagrant provision centos6 in development it will throw error on could not find recipe mysql for cookbook database

The fix is to lock the database version like this

depends 'database', '~> 2.3.1'

I will send a pull request soon.

related to #59

@linc01n linc01n added the bug label Feb 10, 2015
@linc01n linc01n self-assigned this Feb 10, 2015
This was referenced Feb 10, 2015
linc01n added a commit that referenced this issue Feb 11, 2015
Lock database cookbook to 2.3.1
@patcon
Copy link
Collaborator

patcon commented Jul 5, 2015

I think mysql2_chef_gem cookbook was just split out of the database cookbook, but that should be a pretty quick fix. Would be great to get to working with newer database cookbooks, as right now the very strict cookbook requirement is making berkshelf dependency resolution unhappy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants