"Could not resolve the dependencies" error #42
Comments
|
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. |
|
Having a similar issue with |
|
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 : 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 : Any suggestions ? |
|
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 : And the error : The conflict detected is strange : 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) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: