-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Git status: 128 #50
Comments
Same issue trying to register Sizzle. I must be doing something wrong. bower cloning git://github.com/jquery/sizzle.git
bower cached git://github.com/jquery/sizzle.git
bower fetching sizzle
bower error Git status: 128 |
Ah, my guess is that the url should be different for those who are owners of the repo. Seems to work for everybody besides Sizzle members. I wonder if this is a bigger issue that bower needs to address somehow. Perhaps the https protocol rather than the git one would work for everyone. |
Hmm.. Owner shouldn't matter at all, actually.. |
Yea, I get the same error with all urls and combinations. From what I can find, 128 seems to be a permissions error. Regular git clone works fine tho. |
Well, I removed my bower cache and it works for me now. I don't know if that will help anyone. Perhaps bower didn't cache something correctly when I was registering sizzle.
|
Very nice, this also works for me. |
Hm, i've also registered angular-ui and installed the package. Everything works as expected, but the yeoman script ends up with "Git status: 127 " - 127 means "command not found" ... am i right? |
hm interesting… we will definitely be adding a -f flag in the future which does a hard reinstall and blows away your cache. would be nice to know why you guys were getting the 128 tho |
I also ran into this issue. I had previously installed the package with a full git URL. I then registered the package and tried to reinstall it via bower's registry. This is when I got the 128 error.
I then manually cleared my cache at This time I got the error:
Just for laughs, I re-ran the installation and it exited cleanly. Thinking that was odd, I manually cleared the cache again and tried to reinstall. Everything installed correctly this time and bower exited cleanly. I'm only posting this in case someone else runs into the same series of events and it proves useful to someone. |
@dlindahl it seems you are using an old version of bower. You now got a -f flag, a new cache clean command and a new cache strategy. |
Still unresolved as of version 0.3.2. I just registered a package ('konami'). I was able to install it once. All other attempts after that, both on windows and mac result in code 128. I tried both |
@remcoder The url you registered is wrong. You registered with: git://github.com:remcoder/konami.git |
@remcoder Should be changed, can you please check if it works? |
@satazor This is why we need better validation. |
oh sorry, my bad. Indeed it works now! Thx. |
@sindresorhus True |
I was facing the same problem on windows .But i ran command bower cache-clean and i was able to install angular.js using bower properly |
Under windows goto: and clear all content in cache folder. |
I just run 'bower cache-clean'! |
i still get status 128 when trying to install requirejs. I also tried doing a fresh install of bower, as well as cleaning my cache. Still giving me the 128 error. what I run:
what I get:
I am running Windows 7 |
EDIT ok, I realized my problem. I was having the same exact issue with the status 128, unable to connect to github.com, etc. I realized I'm on WiFi, and one of the access points explicitly blocks port 22. My adapter had switched, and that was the reason. Switched it back to open WiFi and voila, works again. Just another data point to consider if you're getting this error...check your network, man. |
Hello guys I´d thinking about comments and davsford, he is correct. Bower uses git:// by default so I just get the URL with https:// provided on page of each project inside of zip button for download. root@labntiX: It´s working fine now! |
I came across this problem while using the Angular generator on my university Wifi network. It was driving me nuts until I found the suggestion by @davisford . I am now at home and magically bower works just fine. There is a workaround that makes git always use https (source): git config --global url."https://".insteadOf git:// |
Hi. I've checked my WiFi AP and the port 22 is open. The port seems open in the firewall too (i'm using the default mac firewall) but I still get the same error. I used the workaround posted by @jcumminsr1 and everything worked out fine, but IMO not using the git native protocol feels wrong. |
Apparently, bower has permissions issues with this: bower/bower#50 The recommended fix is to use https urls.
@renjithkv123 brilliant, that fixes everything. Thanks! |
Deleting C:\user\AppData\Roaming\bower\cache did it for me. |
I came around that issue while searching for the Git error code Edit: For later readers: Make sure you are providing credentials when using |
@jcumminsr1 - thanks for the tip. git config worked for me git config --global url."https://".insteadOf git:// |
@jcumminsr1 - thanks for the tip. git config worked for me[2] |
Make sure "telnet github.com 9418" from a command prompt works. If it doesn't, you have firewall issues. (I got the code 128 error on Windows, because of a corporate firewall) |
Thanks! Tip below helped! BTW not only on Mac, I'm on Windows #mac only |
like @renjithvincent said, git config --global url."https://".insteadOf git:// |
thanks @renjithvincent, |
Thanks, this helped me :) |
faced the problem a moment ago,
I was trying to install the module from a public github repo with Even i m the owner, i got I had to change for explicit http The module would install. I also tried Maybe i did something wrong, only sharing. |
Maybe this will help someone someday, but also be sure you aren't simply using an old version of bower. I tried every solution here plus adding "strict-ssl": false, "https-proxy": "" to the .bowerrc, with no dice. Then I noticed the Windows box I had recently switched over to was running bower 1.4.1. Upgrading to 1.7.9 resolved it. |
git config --global url."https://".insteadOf git:// worked for me. thnx |
Same issue here, I'd like to note that e.g. |
after git config --global url."https://".insteadOf git:// this git push is not working for me. |
Hey guys,
just registered a new package a few minutes ago.
When i want to install it, i'm getting an error "Git status: 128"
The package is 'underscore.string':
git://github.com/epeli/underscore.string.git
The solution in issue #32 doesn't work for me.
Could you help with this?
Thanks in advance!
The text was updated successfully, but these errors were encountered: