Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error message when resolving conflics #314

Open
deric opened this issue Jul 15, 2015 · 2 comments
Open

Better error message when resolving conflics #314

deric opened this issue Jul 15, 2015 · 2 comments

Comments

@deric
Copy link

deric commented Jul 15, 2015

When trying librarian-puppet update it's really complicated to find out the cause of all the conflict. The error message is not helpful at all:

Could not resolve the dependencies.

even when running with verbose flag:

[Librarian] Conflict between puppetlabs-apt (>= 2.0.1) <https://forgeapi.puppetlabs.com> and puppetlabs-apt (< 2.0.0, >= 1.4.0) <https://forgeapi.puppetlabs.com>

it's not clear which module requested which version. Would it be possible to print that information?

e.g.

module puppet-foo(0.3.1) requires puppetlabs-apt (< 2.0.0)
however puppet-bar(xxxxx) requires puppetlabs-apt (> 2.0.1) 
@carlossg
Copy link
Collaborator

PRs welcome

@petems
Copy link
Contributor

petems commented Sep 19, 2017

I actually had a look into this as I hit the same issue, but it's actually in the upstream library rather than this gem and seemed a little complicated to solve, unfortunately.

I ended up making a quick script to show all the dependencies from a Puppetfile, then use that to help show where the conflicts come from, not perfect but maybe it will help someone else? https://github.com/petems/puppet-module-dependancy-lister

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

No branches or pull requests

3 participants