Closed cdenneen closed 9 years ago
You have strict requirements that can not be satisfied, you shouldn't use exact versions unless you really really need them In this case elasticsearch-elasticsearch 0.1.0 does not exist
@carlossg where in the output does it show that. It was available on forge at one point but appears to have been removed. Is there anyway to have librarian do better error reporting so I know exactly where to look? Tag still exists in github repo so If error was clearer I could just update Puppetfile to reflect GitHub URL and tag. It would greatly help when converting monolithic repo like this to Puppetfile.
@electrical can you shed some light as to why certain versions would be removed from forge? This obviously breaks things for people still requiring old versions of modules for compliance reasons and using librarian-puppet Puppetfile workflow (r10k or not).
@cdenneen 0.1.0 never existed under the 'elasticsearch' account but under my personal one 'ispavailability'. At 0.2.0 i moved it to the elasticsearch account.
Hope this helps.
P.s 0.1.0 is extremely old as we are now at 0.4.0
@cdenneen there is no good output but that's the way it is with underlying librarian gem
Module elasticsearch-elasticsearch found versions: 0.4.0, 0.3.2, 0.3.1, 0.3.0, 0.2.4, 0.2.3, 0.2.2, 0.2.1, 0.2.0
You could remove modules until it resolves to narrow down the problem
I chose to test these 2 since the Librarian verbose output below says
Failed to resolv
It has something to do with the Puppetfile syntax of puppetlabs-apache vs puppetlabs/apache I'm guessing because if I change the entire Puppetfile from - to / I get modules like apache and apt that failed below to succeed and others that succeeded before to fail it seems.
If someone could help me understand this I'd really appreciate it.