Open elliotblackburn opened 7 years ago
elliotblackburn
commented
7 years ago Update:
I've tried recreating this in a new directory with no other modules and I can't seem to recreate the issue at that level. Any ideas what might be going on, I can't for the life of me get it installing and the same error keeps coming up.
BarnumD
commented
6 years ago Having a similar issue with mod 'puppetlabs/concat', '3.0.0'
GilgOuille
commented
4 years ago Hi,
There's my configuration :
And this is an entry in my Puppetfile that it can't resolve version:
mod 'herculesteam-augeasproviders_shellvar', '4.0.0'Here the stdout of the install command :
[Librarian] Resolving herculesteam-augeasproviders_shellvar (= 4.0.0) <https://forgeapi.puppetlabs.com>
[Librarian] Checking manifests
[Librarian] Module herculesteam-augeasproviders_shellvar found versions: 4.0.0, 3.1.0, 3.0.0, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.4, 2.0.2, 2.0.1, 2.0.0
[Librarian] Checking herculesteam-augeasproviders_shellvar/4.0.0 <https://forgeapi.puppetlabs.com>
[Librarian] Conflict between herculesteam-augeasproviders_shellvar/4.0.0 <https://forgeapi.puppetlabs.com> and herculesteam-augeasproviders_shellvar (~> 2.0) <https://forgeapi.puppetlabs.com>
[Librarian] Backtracking from herculesteam-augeasproviders_shellvar/4.0.0 <https://forgeapi.puppetlabs.com>
[Librarian] Checking herculesteam-augeasproviders_shellvar/3.1.0 <https://forgeapi.puppetlabs.com>
[Librarian] Conflict between herculesteam-augeasproviders_shellvar/3.1.0 <https://forgeapi.puppetlabs.com> and herculesteam-augeasproviders_shellvar (= 4.0.0) <https://forgeapi.puppetlabs.com>
[Librarian] Backtracking from herculesteam-augeasproviders_shellvar/3.1.0 <https://forgeapi.puppetlabs.com>I don't know what Librarian is querying to forgeapi, but we target version 4.0.0 of the module, forgeapi sent the available versions, and when Librarian compare with the target version : it outputs herculesteam-augeasproviders_shellvar (~> 2.0).
Then, he tries all versions without success, of course.
I have too the same behaviour with :
mod 'puppetlabs-apt', '7.3.0'Here's the stack trace :
Could not resolve the dependencies.
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/action/persist_resolution_mixin.rb:11:in `persist_resolution'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/action/resolve.rb:32:in `run'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/action/resolve.rb:10:in `run'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/cli.rb:104:in `resolve!'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/cli.rb:68:in `install'
/home/didier.bourriaud/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/home/didier.bourriaud/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/home/didier.bourriaud/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/home/didier.bourriaud/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `block (2 levels) in bin!'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:31:in `returning_status'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `block in bin!'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:47:in `with_environment'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `bin!'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/bin/librarian-puppet:7:in `<top (required)>'
/usr/local/bin/librarian-puppet:23:in `load'
/usr/local/bin/librarian-puppet:23:in `<main>'Any suggestions ?
igalic
commented
4 years ago re,
mod 'herculesteam-augeasproviders_shellvar', '4.0.0'does anything else in your tree depend on that module?
GilgOuille
commented
4 years ago re,
mod 'herculesteam-augeasproviders_shellvar', '4.0.0'does anything else in your tree depend on that module?
We use a huge Puppetfile which mix Puppet Forge and some private repository. Do you know how I can show if a declared module in my Puppetfile is already a dependancy with another version ?
I'm pretty new with librarian-puppet, our Puppetfile in our CI/CD is process by R10K. I use this tool in Rubymine feature.
I attach the error pretty similar with puppetlabs-apt.
In the Puppetfile :
mod 'puppetlabs-apt', '7.3.0'And the error :
[Librarian] Resolving puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:168:in `scope_resolving_dependency']
[Librarian] Checking manifests [lib/librarian/resolver/implementation.rb:184:in `scope_checking_manifests']
[Librarian] Module puppetlabs-apt found versions: 7.4.2, 7.4.1, 7.4.0, 7.3.0, 7.2.0, 7.1.0, 7.0.1, 7.0.0, 6.3.0, 6.2.1, 6.2.0, 6.1.1, 6.1.0, 6.0.0, 5.0.1, 5.0.0, 4.5.1, 4.5.0, 4.4.1, 4.4.0, 4.3.0, 4.2.0, 4.1.0, 4.0.0, 3.0.0, 2.4.0, 2.3.
0, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.1, 2.0.0, 1.8.0, 1.7.0, 1.6.0, 1.5.2, 1.5.0, 1.4.2, 1.4.0, 1.3.0, 1.2.0, 1.1.1, 1.1.0, 1.0.1, 1.0.0, 0.0.4, 0.0.3 [../librarian-puppet-3.0.0/lib/librarian/puppet/source/forge/repo.rb:19:in `versio
ns']
[Librarian] Checking puppetlabs-apt/7.4.2 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:191:in `scope_checking_manifest']
[Librarian] Conflict between puppetlabs-apt/7.4.2 <https://forgeapi.puppetlabs.com> and puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
[Librarian] Backtracking from puppetlabs-apt/7.4.2 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:198:in `block in scope_checking_manifest']
[Librarian] Checking puppetlabs-apt/7.4.1 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:191:in `scope_checking_manifest']
[Librarian] Conflict between puppetlabs-apt/7.4.1 <https://forgeapi.puppetlabs.com> and puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
[Librarian] Backtracking from puppetlabs-apt/7.4.1 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:198:in `block in scope_checking_manifest']
[Librarian] Checking puppetlabs-apt/7.4.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:191:in `scope_checking_manifest']
[Librarian] Conflict between puppetlabs-apt/7.4.0 <https://forgeapi.puppetlabs.com> and puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
[Librarian] Backtracking from puppetlabs-apt/7.4.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:198:in `block in scope_checking_manifest']
[Librarian] Checking puppetlabs-apt/7.3.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:191:in `scope_checking_manifest']
[Librarian] Conflict between puppetlabs-apt/7.3.0 <https://forgeapi.puppetlabs.com> and puppetlabs-apt (< 7.0.0, >= 2.0.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
[Librarian] Backtracking from puppetlabs-apt/7.3.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:198:in `block in scope_checking_manifest']
[Librarian] Checking puppetlabs-apt/7.2.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:191:in `scope_checking_manifest']
[Librarian] Conflict between puppetlabs-apt/7.2.0 <https://forgeapi.puppetlabs.com> and puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
[Librarian] Backtracking from puppetlabs-apt/7.2.0 <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:198:in `block in scope_checking_manifest']
...
...
[Librarian] Failed to resolve puppetlabs-apt (= 7.3.0) <https://forgeapi.puppetlabs.com> [lib/librarian/resolver/implementation.rb:177:in `block in scope_resolving_dependency']
Could not resolve the dependencies.
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/action/persist_resolution_mixin.rb:11:in `persist_resolution'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/action/resolve.rb:32:in `run'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/action/resolve.rb:10:in `run'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/cli.rb:104:in `resolve!'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/lib/librarian/puppet/cli.rb:68:in `install'
/home/xxxxxxx/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/home/xxxxxxx/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/home/xxxxxxx/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/home/xxxxxxx/.gem/ruby/2.5.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `block (2 levels) in bin!'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:31:in `returning_status'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `block in bin!'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:47:in `with_environment'
/var/lib/gems/2.5.0/gems/librarianp-1.0.0/lib/librarian/cli.rb:26:in `bin!'
/var/lib/gems/2.5.0/gems/librarian-puppet-3.0.0/bin/librarian-puppet:7:in `<top (required)>'
/usr/local/bin/librarian-puppet:23:in `load'
/usr/local/bin/librarian-puppet:23:in `<main>'The conflict detected is strange : Conflict between puppetlabs-apt/7.3.0 https://forgeapi.puppetlabs.com and puppetlabs-apt (< 7.0.0, >= 2.0.0) https://forgeapi.puppetlabs.com [lib/librarian/resolver/implementation.rb:209:in `debug_conflict']
All others rule try to match our required version. But when librarian try to chech the target version, he changes the rules --> puppetlabs-apt (< 7.0.0, >= 2.0.0)
First of all, I'm using librarian through the vagrant-librarian-puppet plugin. I don't think it should have a huge bearing but it might do, the box I'm trying to run on is a ubuntu/trusty64.
I have a Puppetfile (shown below) which has been working just fine for months, my environment hasn't changed and I'm able to tear down the box and rebuild with no problems at all. However I'm now wishing to add MongoDB to my environment so I decided to add
puppetlabs/mongodbto my Puppet file. I'm not even calling the class anywhere in my code an error which simply says "Could not resolve the dependencies". My project already has amodulesdirectory with all the dependencies except this new addition and I've even tried clearing that but it doesn't seem to have had any impact.What's more is I've tried a few other Monogdb modules from puppet forge and it's having the same issue. However when it pulls down all of current dependencies it seems to be just fine.
Any thoughts would be much appreciated, do also let me know if you need more information that I've not provided already.
Below is my Puppetfile, followed by the line I'm adding to the bottom of it to include
pupeptlabs/monogdbas well as the full stack trace.Puppetfile (works totally fine)
Additional line being appended (causes an error)
Error and stack trace
The stack trace