-
Notifications
You must be signed in to change notification settings - Fork 211
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
Inconsistent duplicate dependency resolution #316
Comments
can you try in another machine with ruby 1.9+ and latest librarian-puppet version to see if it behaves differently ? |
It seems to resolve the dependencies as expected on my MBP running Ruby 2.2.1, librarian-puppet 2.2.0 and librarianp 0.6.3...
However that doesn't help when I'm trying to run beaker tests using librarian-puppet on CentOS 6 hosts :( Edit: I also thought that the dependency resolution was a function of librarianp rather than librarian-puppet, and those are the same version across both hosts... |
I've merged master into 1.x, you can try if the latest there works |
Better, but still not perfect...
I thought the dependency resolution is a function of librarianp rather than librarian-puppet, so surely the version of that should be all that matters? Cheers |
yes, most likely. Take a look at voxpupuli/librarian@befb958 I'm not sure when I'll have time to look at it, so if you want to try to send a PR... |
OK, I'll see if I can find where the issue is... Cheers |
Afternoon
I'm currently using Librarian-Puppet 1.5.0 with librarianp 0.6.3 on a Centos 6 host which is restricted to Ruby 1.8.7...
I seem to be experiencing inconsistent dependency resolution, as per the following log: https://gist.github.com/fatmcgav/700f9d8be6950f593eb6#file-librarian-puppet-20install-20log
As you can see from the Puppetfile, all 4 modules are over-ridden from the metadata.json file.
However 2 are being resolved to the forge, and 2 to github...
Any idea how I can get all 4 to resolve to their Github links?
Cheers
Gavin
The text was updated successfully, but these errors were encountered: