# Strategies for debugging with dependency resolution issues?

**URL:** <https://discourse.chef.io/t/strategies-for-debugging-with-dependency-resolution-issues/7366>\
**Category:** Chef Infra (archive)\
**Created:** [November 25, 2015, 4:33pm UTC](https://discourse.chef.io/t/strategies-for-debugging-with-dependency-resolution-issues/7366 "2015-11-25T16:33:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![martinb3](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/martinb3/32/34_2.png) [@martinb3](https://discourse.chef.io/u/martinb3)\
**Post date:** [November 30, 2015, 10:13pm UTC](https://discourse.chef.io/t/strategies-for-debugging-with-dependency-resolution-issues/7366/4 "2015-11-30T22:13:19Z")

</div>

You might also try the latest Berkshelf and solve gems which contain some fixes, e.g.:

Gemfile:

```auto
gem 'berkshelf', git: 'git@github.com:berkshelf/berkshelf.git'
gem 'solve', git: 'git@github.com:berkshelf/solve.git'

```

If you did that, you could try forcing Berkshelf to use the ruby resolver in your Berksfile:

```auto
solver :ruby, :required

```

That might give you some additional clues. But otherwise, not sure how to suggest you debug the gecode solver, and it sounds like you can’t give us an example since they’re internal cookbooks.

---

_[View the full topic](https://discourse.chef.io/t/strategies-for-debugging-with-dependency-resolution-issues/7366)._