Closed dkingofpa closed 11 years ago
It appears to be the resolver trying all possible combinations of all cookbooks in order, looking for a consistent resolution (yes we can improve this). You may want to find out what's depending on mysql >= 1.3.0
though, or use a mysql cookbook marked as 1.3.0
or higher.
Librarian was running for over ten minutes so I had to ctrl-c it. As soon as it finds a cookbook conflict, perhaps it can just fail fast?
Opscode's database cookbook bumped it's mysql cookbook dependency to >= 1.3.0. I resolved that issue and librarian ran fine.
I would like to improve the dependency resolver. But for now, glad to hear you've worked around it.
I've made some changes to the resolver. If you can still reproduce the problem with librarian-v0.0.25, mind giving it a try with master >= 0019611?
Sure, I'm still able to reproduce the issue with an older version of my project and librarian-v0.0.25:
git clone git@github.com:xforty/vagrant-drupal.git
cd vagrant-drupal
git checkout 0.4.0
rm Cheffile.lock
librarian-chef install --verbose
Problem reproduced...keeps trying all possible cookbook combinations.
I then cloned librarian's master branch (HEAD currently at SHA 34eaa6b4ed) and ran it using the instructions from your readme:
rm -rf tmp
git clone git://github.com/applicationsonline/librarian.git
librarian/bin/librarian-chef install --verbose
Appears like that fixed it. Here's the output: https://gist.github.com/4159026
Fantastic. Thanks!
Using 0.0.25, I'm running
librarian-chef install --verbose
with this Cheffile. I'm getting a conflict with the mysql cookbook which appears to be causing an infinite loop. It just keeps checking the aws cookbook and then trying to resolve mysql. Here's a snippet of the output: