-
Notifications
You must be signed in to change notification settings - Fork 40
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
More information about conflicting dependencies #16
Comments
+1 It's really frustrating to manually dig into tons of |
Is anybody looking after this project anymore? :( |
I'm facing the same problem, and it seams a hard one to solve. The exception is thrown from inside librarian, not librarian-puppet. I've tried to find out where the conflict comes from but my lack of knowledge about how librarian works stopped me. |
As a work around I did this to have a better visualization of the problems: |
PR #68 should help address this issue. |
This is a really annoying problem. Trial-and-error debugging of puppet module conflicts are pretty time consuming procedure. If a unresolvable dependency problem appears, it would be very helpful if "librarian-puppet" would show all modules which are requesting the dependency combined with their version constraints. Currently i get the following output:
|
#68 has been merged. |
In this particular case, I tried to pull a newer release of puppetlabs-apt (2.2.2)
together with puppetlabs-postgres 4.1.0 (legacy project being updated, hence the bit older release).
There are also many other modules in the Puppetfile which should be pulled, too.
When running librarian-puppet, it aborts with an error:
As the opposing module(s) with the conflicting puppetlabs-apt required version/version constraint
are not logged by librarian-puppet, I had to comment out all modules in Puppetfiles
and re-enable them one by one and re-invoke librarian-puppet each time
in order finding out what else modules are actually conflicting.
It also doesn't seem to be logged anywhere else during the process.
Eventually puppetlabs-postgres 4.1.0 was found being the responsible module
after re-enabling it and encountering the conflict error,
it has been then upgraded to version 4.7.1 which uses a newer puppetlabs-apt dependency version.
If there had been other modules with conflicts I would have had to repeat the debugging multiple times.
It would be very helpful if librarian-puppet logs more detalied information
about modules with conflicting dependencies.
The text was updated successfully, but these errors were encountered: