-
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
ref SHA ambiguous argument #307
Comments
I think that commit was removed from the tree
|
I have the same problem. I also tried the example from the readme (slightly modified): With following result: Git version: 2.1.4 |
@jpmorris issue is the same as #309 trying to get an orphaned commit that is not pulled in a normal clone, may need @dennisgranath your example works fine here, I can't say what's wrong without more details |
Ok! VERSIONS$ ruby --version $ librarian-puppet version $ gem list | grep puppet DistWindows 7 Puppetfile#!/usr/bin/env ruby forge "https://forgeapi.puppetlabs.com" mod 'puppetlabs-apt', LOG~/src/lib-pup-bug$ librarian-puppet --verbose install |
Have you deleted the If you did, go into
|
Everything looks fine when running; But librarian-puppet output I see: So I tried this: So I started to suspect that something was wrong with my git installation (which I installed using cygwins package manager). I uninstalled it and re-installed "windows way" and that seems to work:) |
I guess there is some issue with windows shell execution that removes the curly brackets around |
Im having the same issue and it does the same thing even when i execute under the bash(mingw) shell. |
Workaround for me is to double escape the curly braces:
Obviously this could break linux-builds and is probably required elsethere, too. |
With no Puppetfile.lock and a Puppetfile that contains:
(Or with the full SHA.) I get the error:
The text was updated successfully, but these errors were encountered: