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

Closed
D3CK3R opened this Issue Sep 14, 2012 · 51 comments

Comments

Projects
None yet
@D3CK3R

D3CK3R commented Sep 14, 2012

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!

@timmywil

This comment has been minimized.

Show comment
Hide comment
@timmywil

timmywil Sep 14, 2012

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

timmywil commented Sep 14, 2012

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
@timmywil

This comment has been minimized.

Show comment
Hide comment
@timmywil

timmywil Sep 14, 2012

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.

timmywil commented Sep 14, 2012

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.

@paulirish

This comment has been minimized.

Show comment
Hide comment
@paulirish

paulirish Sep 14, 2012

Member

Hmm.. Owner shouldn't matter at all, actually..

Member

paulirish commented Sep 14, 2012

Hmm.. Owner shouldn't matter at all, actually..

@timmywil

This comment has been minimized.

Show comment
Hide comment
@timmywil

timmywil Sep 14, 2012

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.

timmywil commented Sep 14, 2012

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.

@timmywil

This comment has been minimized.

Show comment
Hide comment
@timmywil

timmywil Sep 14, 2012

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.

#mac only
rm -rf ~/.bower

timmywil commented Sep 14, 2012

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.

#mac only
rm -rf ~/.bower
@D3CK3R

This comment has been minimized.

Show comment
Hide comment
@D3CK3R

D3CK3R Sep 15, 2012

Very nice, this also works for me.
Will this be fixed in a future release?

D3CK3R commented Sep 15, 2012

Very nice, this also works for me.
Will this be fixed in a future release?

@D3CK3R

This comment has been minimized.

Show comment
Hide comment
@D3CK3R

D3CK3R Sep 15, 2012

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?

D3CK3R commented Sep 15, 2012

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?

@fat

This comment has been minimized.

Show comment
Hide comment
@fat

fat Sep 16, 2012

Contributor

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

Contributor

fat commented Sep 16, 2012

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

@dlindahl

This comment has been minimized.

Show comment
Hide comment
@dlindahl

dlindahl Nov 1, 2012

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.

error: unable to write sha1 filename /Users/dlindahl/.bower/barcode_input/.git/objects/pack/pack-96e63e79ad3802064c429e7443b9eae4f0dd8b7b.pack: No such file or directory

fatal: cannot store pack file

fatal: index-pack failed

bower error Git status: 128

I then manually cleared my cache at ~/.bower as suggested and tried again.

This time I got the error:

bower copying /Users/dlindahl/.bower/barcode_input

events.js:68
        throw arguments[1]; // Unhandled 'error' event
                   ^
Error: ENOENT, open '/var/folders/5V/5VYhoyUTGKiqL+FlYJyHRk+++TM/-Tmp-/tmp-40658nvawp8w/.git/hooks/post-receive.sample'

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 commented Nov 1, 2012

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.

error: unable to write sha1 filename /Users/dlindahl/.bower/barcode_input/.git/objects/pack/pack-96e63e79ad3802064c429e7443b9eae4f0dd8b7b.pack: No such file or directory

fatal: cannot store pack file

fatal: index-pack failed

bower error Git status: 128

I then manually cleared my cache at ~/.bower as suggested and tried again.

This time I got the error:

bower copying /Users/dlindahl/.bower/barcode_input

events.js:68
        throw arguments[1]; // Unhandled 'error' event
                   ^
Error: ENOENT, open '/var/folders/5V/5VYhoyUTGKiqL+FlYJyHRk+++TM/-Tmp-/tmp-40658nvawp8w/.git/hooks/post-receive.sample'

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.

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Nov 2, 2012

Member

@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.

Member

satazor commented Nov 2, 2012

@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.

@remcoder

This comment has been minimized.

Show comment
Hide comment
@remcoder

remcoder Nov 8, 2012

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 rm -rf ~/.bower and bower cache-clean to no avail.

remcoder commented Nov 8, 2012

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 rm -rf ~/.bower and bower cache-clean to no avail.

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Nov 9, 2012

Member

@remcoder The url you registered is wrong.

You registered with: git://github.com:remcoder/konami.git
I'll change it to: git://github.com/remcoder/konami.git

Member

satazor commented Nov 9, 2012

@remcoder The url you registered is wrong.

You registered with: git://github.com:remcoder/konami.git
I'll change it to: git://github.com/remcoder/konami.git

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor

satazor Nov 9, 2012

Member

@remcoder Should be changed, can you please check if it works?

Member

satazor commented Nov 9, 2012

@remcoder Should be changed, can you please check if it works?

@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Nov 9, 2012

Member

@satazor This is why we need better validation.

Member

sindresorhus commented Nov 9, 2012

@satazor This is why we need better validation.

@remcoder

This comment has been minimized.

Show comment
Hide comment
@remcoder

remcoder Nov 9, 2012

oh sorry, my bad. Indeed it works now! Thx.

remcoder commented Nov 9, 2012

oh sorry, my bad. Indeed it works now! Thx.

@satazor

This comment has been minimized.

Show comment
Hide comment
@satazor
Member

satazor commented Nov 9, 2012

@ajaybeniwal

This comment has been minimized.

Show comment
Hide comment
@ajaybeniwal

ajaybeniwal Nov 17, 2012

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

ajaybeniwal commented Nov 17, 2012

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

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Mar 4, 2013

Under windows goto:
C:\Users\AppData\Roaming\bower\cache\

and clear all content in cache folder.

ghost commented Mar 4, 2013

Under windows goto:
C:\Users\AppData\Roaming\bower\cache\

and clear all content in cache folder.

@hushicai

This comment has been minimized.

Show comment
Hide comment
@hushicai

hushicai Mar 5, 2013

I just run 'bower cache-clean'!

hushicai commented Mar 5, 2013

I just run 'bower cache-clean'!

@andvik

This comment has been minimized.

Show comment
Hide comment
@andvik

andvik May 9, 2013

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:

bower install requirejs

what I get:

bower cloning git://github.com/jrburke/requirejs
bower caching git://github.com/jrburke/requirejs
bower error status code of git: 128

There were errors, here's a summary of them:
- requirejs status code of git: 128
fata: unable to connect to github.com:
github.com[0: 204.232.175.90] errno= No error

I am running Windows 7

andvik commented May 9, 2013

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:

bower install requirejs

what I get:

bower cloning git://github.com/jrburke/requirejs
bower caching git://github.com/jrburke/requirejs
bower error status code of git: 128

There were errors, here's a summary of them:
- requirejs status code of git: 128
fata: unable to connect to github.com:
github.com[0: 204.232.175.90] errno= No error

I am running Windows 7

@davisford

This comment has been minimized.

Show comment
Hide comment
@davisford

davisford May 13, 2013

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.

davisford commented May 13, 2013

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.

@Brainux

This comment has been minimized.

Show comment
Hide comment
@Brainux

Brainux May 13, 2013

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:# bower install https://github.com/yeoman/stringify-object.git
bower cloning https://github.com/yeoman/stringify-object.git
bower caching https://github.com/yeoman/stringify-object.git
bower fetching stringify-object
bower checking out stringify-object#0.1.3
bower warn Package stringify-object is still using the deprecated "component.json" file
bower copying /root/.bower/cache/stringify-object/71340b9c4891690500ab7e6cc5ee0866
bower installing stringify-object#0.1.3
root@labntiX:
# bower install https://github.com/blueimp/jQuery-File-Upload.git
bower cloning https://github.com/blueimp/jQuery-File-Upload.git
bower caching https://github.com/blueimp/jQuery-File-Upload.git
bower fetching jQuery-File-Upload
bower checking out jQuery-File-Upload#8.1.0
bower copying /root/.bower/cache/jQuery-File-Upload/8f1a2144e5c532c8357197e9c60a1fee
bower installing jQuery-File-Upload#8.1.0

It´s working fine now!

Brainux commented May 13, 2013

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:# bower install https://github.com/yeoman/stringify-object.git
bower cloning https://github.com/yeoman/stringify-object.git
bower caching https://github.com/yeoman/stringify-object.git
bower fetching stringify-object
bower checking out stringify-object#0.1.3
bower warn Package stringify-object is still using the deprecated "component.json" file
bower copying /root/.bower/cache/stringify-object/71340b9c4891690500ab7e6cc5ee0866
bower installing stringify-object#0.1.3
root@labntiX:
# bower install https://github.com/blueimp/jQuery-File-Upload.git
bower cloning https://github.com/blueimp/jQuery-File-Upload.git
bower caching https://github.com/blueimp/jQuery-File-Upload.git
bower fetching jQuery-File-Upload
bower checking out jQuery-File-Upload#8.1.0
bower copying /root/.bower/cache/jQuery-File-Upload/8f1a2144e5c532c8357197e9c60a1fee
bower installing jQuery-File-Upload#8.1.0

It´s working fine now!

@jcumminsr1

This comment has been minimized.

Show comment
Hide comment
@jcumminsr1

jcumminsr1 May 22, 2013

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://

jcumminsr1 commented May 22, 2013

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://
@marcoslhc

This comment has been minimized.

Show comment
Hide comment
@marcoslhc

marcoslhc May 23, 2013

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.

marcoslhc commented May 23, 2013

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.

@andvik

This comment has been minimized.

Show comment
Hide comment
@andvik

andvik May 23, 2013

@jcumminsr1 - I used the workaround and now it works :) chances are that its the firewall settings at work. But yea, thats a good workaround for people who still experience this problem.

andvik commented May 23, 2013

@jcumminsr1 - I used the workaround and now it works :) chances are that its the firewall settings at work. But yea, thats a good workaround for people who still experience this problem.

@marcoslhc

This comment has been minimized.

Show comment
Hide comment
@marcoslhc

marcoslhc May 24, 2013

I've shut down the firewall and the error still came up.

The thing is why is this issue closed if the error still shows up? The workaround is fine while the issue get solved, but I don't think developers should change the git global configuration just because Bower doesn't get along with git:// protocol. If the case is Bower works with https:// only then the installer should make sure https:// is used in that particular git instance. It should be transparent to the user.

I don't know if I'm explaining myself right but it makes sense to me.

marcoslhc commented May 24, 2013

I've shut down the firewall and the error still came up.

The thing is why is this issue closed if the error still shows up? The workaround is fine while the issue get solved, but I don't think developers should change the git global configuration just because Bower doesn't get along with git:// protocol. If the case is Bower works with https:// only then the installer should make sure https:// is used in that particular git instance. It should be transparent to the user.

I don't know if I'm explaining myself right but it makes sense to me.

@jcumminsr1

This comment has been minimized.

Show comment
Hide comment
@jcumminsr1

jcumminsr1 May 24, 2013

I completely agree. A 'use https' flag seems like it would be one way to do
it. Another way would be a fallback method. On the first clone that fails
using git, bower could try https, only if that clone then succeeds then it
would set the 'use https' flag for the rest of the batch.

On Thursday, May 23, 2013, Marcos Hernández wrote:

I've shut down the firewall and the error still came up.

The thing is why is this issue closed if the error still shows up? The
workaround is fine while the issue get solved, but I don't think developers
should change the git global configuration just because Bower doesn't get
along with git:// protocol. If the case is Bower works with https:// only
then the installer should make sure https:// is used in that particular
git instance.

I don't know if I'm explaining myself right but it makes sense to me.


Reply to this email directly or view it on GitHubhttps://github.com/bower/bower/issues/50#issuecomment-18379325
.

Jim Cummins
Front End Developer Intern
relationship | one

OFFICE: 763.355.1025
DIRECT: 763.555.1025 ext. 121
www.relationshipone.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.

jcumminsr1 commented May 24, 2013

I completely agree. A 'use https' flag seems like it would be one way to do
it. Another way would be a fallback method. On the first clone that fails
using git, bower could try https, only if that clone then succeeds then it
would set the 'use https' flag for the rest of the batch.

On Thursday, May 23, 2013, Marcos Hernández wrote:

I've shut down the firewall and the error still came up.

The thing is why is this issue closed if the error still shows up? The
workaround is fine while the issue get solved, but I don't think developers
should change the git global configuration just because Bower doesn't get
along with git:// protocol. If the case is Bower works with https:// only
then the installer should make sure https:// is used in that particular
git instance.

I don't know if I'm explaining myself right but it makes sense to me.


Reply to this email directly or view it on GitHubhttps://github.com/bower/bower/issues/50#issuecomment-18379325
.

Jim Cummins
Front End Developer Intern
relationship | one

OFFICE: 763.355.1025
DIRECT: 763.555.1025 ext. 121
www.relationshipone.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.

@Danita

This comment has been minimized.

Show comment
Hide comment
@Danita

Danita May 24, 2013

I'm on Windows 7 (64-bit) using git bash. I've already tried @jcumminsr1 solution and it worked for a while, but it seems that sporadically I still get that "128" error back. I'm working on a very large enterprise network, and messing with the firewall settings is received with much reluctancy, so it would be really useful to have the option to specify which protocol to use.

Danita commented May 24, 2013

I'm on Windows 7 (64-bit) using git bash. I've already tried @jcumminsr1 solution and it worked for a while, but it seems that sporadically I still get that "128" error back. I'm working on a very large enterprise network, and messing with the firewall settings is received with much reluctancy, so it would be really useful to have the option to specify which protocol to use.

@mirontoli

This comment has been minimized.

Show comment
Hide comment
@mirontoli

mirontoli Jun 4, 2013

I had this issue when I had bower installed in an app (locally). When I uninstalled it and installed it globally, the problem was gone:
npm uninstall bower
npm install -g bower

Maybe it helps somebody.

mirontoli commented Jun 4, 2013

I had this issue when I had bower installed in an app (locally). When I uninstalled it and installed it globally, the problem was gone:
npm uninstall bower
npm install -g bower

Maybe it helps somebody.

@rbellamy

This comment has been minimized.

Show comment
Hide comment
@rbellamy

rbellamy Jun 9, 2013

I used the global git config change suggested @jcumminsr1, informed by the suggestions by @davisford. I had tried the cache cleaning and the uninstalling/reinstalling of bower to no effect.

git config --global url."http://".insteadOf git://

Here's a snapshot of my session:

[root@xxx Development]# bower install
bower cloning git://github.com/Modernizr/Modernizr.git
bower caching git://github.com/Modernizr/Modernizr.git
bower cloning git://github.com/components/jquery.git
bower cloning git://github.com/jrburke/requirejs
bower cloning git://github.com/jlong/sass-twitter-bootstrap.git
bower caching git://github.com/components/jquery.git
bower caching git://github.com/jrburke/requirejs
bower caching git://github.com/jlong/sass-twitter-bootstrap.git
bower error status code of git: 128
bower error status code of git: 128
bower error status code of git: 128
bower error status code of git: 128

There were errors, here's a summary of them:
- modernizr status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- jquery status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- requirejs status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- sass-bootstrap status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


[root@xxx Development]# git config --global url."http://".insteadOf git://
[root@xxx Development]# bower cache-clean
bower completion cleared completion cache
bower cache cleared jquery
bower cache cleared modernizr
bower cache cleared requirejs
bower cache cleared sass-bootstrap
[root@aergo Development]# bower install
bower cloning git://github.com/jlong/sass-twitter-bootstrap.git
bower caching git://github.com/jlong/sass-twitter-bootstrap.git
bower cloning git://github.com/components/jquery.git
bower caching git://github.com/components/jquery.git
bower cloning git://github.com/Modernizr/Modernizr.git
bower cloning git://github.com/jrburke/requirejs
bower caching git://github.com/Modernizr/Modernizr.git
bower caching git://github.com/jrburke/requirejs
bower fetching jquery
bower checking out jquery#1.9.1
bower warn Package jquery is still using the deprecated "component.json" file
bower copying /root/.bower/cache/jquery/29cb4373d29144ca260ac7c3997f4381
bower fetching requirejs
bower checking out requirejs#2.1.6
bower copying /root/.bower/cache/requirejs/ca377b0e482cd657ed20ebfa063ade1a
bower fetching modernizr
bower fetching sass-bootstrap
bower checking out modernizr#v2.6.2
bower copying /root/.bower/cache/modernizr/49c1c17a4ec1b92db2a4728ece50773a
bower checking out sass-bootstrap#v2.3.2
bower warn Package sass-bootstrap is still using the deprecated "component.json" file
bower copying /root/.bower/cache/sass-bootstrap/f8004d3122cd19e478fcee627c9ad58e
bower cloning git://github.com/components/jquery.git
bower cached git://github.com/components/jquery.git
bower fetching jquery
bower checking out jquery#2.0.2
bower copying /root/.bower/cache/jquery/29cb4373d29144ca260ac7c3997f4381
bower installing jquery#1.9.1
bower installing requirejs#2.1.6
bower installing modernizr#2.6.2
bower installing sass-bootstrap#2.3.2
[root@xxx Development]#

rbellamy commented Jun 9, 2013

I used the global git config change suggested @jcumminsr1, informed by the suggestions by @davisford. I had tried the cache cleaning and the uninstalling/reinstalling of bower to no effect.

git config --global url."http://".insteadOf git://

Here's a snapshot of my session:

[root@xxx Development]# bower install
bower cloning git://github.com/Modernizr/Modernizr.git
bower caching git://github.com/Modernizr/Modernizr.git
bower cloning git://github.com/components/jquery.git
bower cloning git://github.com/jrburke/requirejs
bower cloning git://github.com/jlong/sass-twitter-bootstrap.git
bower caching git://github.com/components/jquery.git
bower caching git://github.com/jrburke/requirejs
bower caching git://github.com/jlong/sass-twitter-bootstrap.git
bower error status code of git: 128
bower error status code of git: 128
bower error status code of git: 128
bower error status code of git: 128

There were errors, here's a summary of them:
- modernizr status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- jquery status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- requirejs status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


- sass-bootstrap status code of git: 128
fatal: unable to connect to github.com:
github.com[0: 204.232.175.90]: errno=Connection timed out


[root@xxx Development]# git config --global url."http://".insteadOf git://
[root@xxx Development]# bower cache-clean
bower completion cleared completion cache
bower cache cleared jquery
bower cache cleared modernizr
bower cache cleared requirejs
bower cache cleared sass-bootstrap
[root@aergo Development]# bower install
bower cloning git://github.com/jlong/sass-twitter-bootstrap.git
bower caching git://github.com/jlong/sass-twitter-bootstrap.git
bower cloning git://github.com/components/jquery.git
bower caching git://github.com/components/jquery.git
bower cloning git://github.com/Modernizr/Modernizr.git
bower cloning git://github.com/jrburke/requirejs
bower caching git://github.com/Modernizr/Modernizr.git
bower caching git://github.com/jrburke/requirejs
bower fetching jquery
bower checking out jquery#1.9.1
bower warn Package jquery is still using the deprecated "component.json" file
bower copying /root/.bower/cache/jquery/29cb4373d29144ca260ac7c3997f4381
bower fetching requirejs
bower checking out requirejs#2.1.6
bower copying /root/.bower/cache/requirejs/ca377b0e482cd657ed20ebfa063ade1a
bower fetching modernizr
bower fetching sass-bootstrap
bower checking out modernizr#v2.6.2
bower copying /root/.bower/cache/modernizr/49c1c17a4ec1b92db2a4728ece50773a
bower checking out sass-bootstrap#v2.3.2
bower warn Package sass-bootstrap is still using the deprecated "component.json" file
bower copying /root/.bower/cache/sass-bootstrap/f8004d3122cd19e478fcee627c9ad58e
bower cloning git://github.com/components/jquery.git
bower cached git://github.com/components/jquery.git
bower fetching jquery
bower checking out jquery#2.0.2
bower copying /root/.bower/cache/jquery/29cb4373d29144ca260ac7c3997f4381
bower installing jquery#1.9.1
bower installing requirejs#2.1.6
bower installing modernizr#2.6.2
bower installing sass-bootstrap#2.3.2
[root@xxx Development]#
@jcumminsr1

This comment has been minimized.

Show comment
Hide comment
@jcumminsr1

jcumminsr1 Jun 10, 2013

@rbellamy Is this on a network that you control? If so, is there any firewall that you're using?

jcumminsr1 commented Jun 10, 2013

@rbellamy Is this on a network that you control? If so, is there any firewall that you're using?

@rbellamy

This comment has been minimized.

Show comment
Hide comment
@rbellamy

rbellamy Jun 10, 2013

@jcumminsr1 It's in an Amazon VPC on an EC2 instance.

rbellamy commented Jun 10, 2013

@jcumminsr1 It's in an Amazon VPC on an EC2 instance.

@whitneyland

This comment has been minimized.

Show comment
Hide comment
@whitneyland

whitneyland Jun 26, 2013

First time user of bower and I'm hitting bunch of issues like this one. Why not just document these in the readme until someone has time to address?

Btw, in my case clearing the cache fixed it. But why, it was my first time installing?

whitneyland commented Jun 26, 2013

First time user of bower and I'm hitting bunch of issues like this one. Why not just document these in the readme until someone has time to address?

Btw, in my case clearing the cache fixed it. But why, it was my first time installing?

@claydiffrient

This comment has been minimized.

Show comment
Hide comment
@claydiffrient

claydiffrient Jul 26, 2013

Using the global replace worked, but shouldn't there be a way to make bower go that way without needing to change the global git configuration?

claydiffrient commented Jul 26, 2013

Using the global replace worked, but shouldn't there be a way to make bower go that way without needing to change the global git configuration?

@afonso-praca

This comment has been minimized.

Show comment
Hide comment
@afonso-praca

afonso-praca Aug 23, 2013

I had this issue when I had bower installed in an app (locally). When I uninstalled it and installed it globally, the problem was gone:

npm uninstall bower
npm install -g bower

afonso-praca commented Aug 23, 2013

I had this issue when I had bower installed in an app (locally). When I uninstalled it and installed it globally, the problem was gone:

npm uninstall bower
npm install -g bower

@renjithvincent

This comment has been minimized.

Show comment
Hide comment
@renjithvincent

renjithvincent Nov 25, 2013

try this on console:

git config --global url."https://".insteadOf git://

This works for me

renjithvincent commented Nov 25, 2013

try this on console:

git config --global url."https://".insteadOf git://

This works for me

mikeschuld pushed a commit to Foundant/fine-uploader that referenced this issue Jan 23, 2014

fix(bower.json): Use https:// rather than git:// protocol
Apparently, bower has permissions issues with this:
bower/bower#50

The recommended fix is to use https urls.
@fantunes

This comment has been minimized.

Show comment
Hide comment
@fantunes

fantunes Feb 26, 2014

@renjithkv123 brilliant, that fixes everything. Thanks!

fantunes commented Feb 26, 2014

@renjithkv123 brilliant, that fixes everything. Thanks!

@kyro38

This comment has been minimized.

Show comment
Hide comment
@kyro38

kyro38 Mar 12, 2014

Deleting C:\user\AppData\Roaming\bower\cache did it for me.

kyro38 commented Mar 12, 2014

Deleting C:\user\AppData\Roaming\bower\cache did it for me.

@franz-josef-kaiser

This comment has been minimized.

Show comment
Hide comment
@franz-josef-kaiser

franz-josef-kaiser May 2, 2014

I came around that issue while searching for the Git error code 128 for a Vagrant/Puppet/Git stack (no bower in there). What I noticed: It only happens when the directory already is in place, therefore clearing the referenced cache works. It seems that it is neither a git:// vs. https:// or unauthenticated request nor a port issue. Btw, I run git version 1.7.9.5 just FYI. Hope this helps someone who stumbles upon it.

Edit: For later readers: Make sure you are providing credentials when using git:// or git@ pointers. Also check your SSH keys.

franz-josef-kaiser commented May 2, 2014

I came around that issue while searching for the Git error code 128 for a Vagrant/Puppet/Git stack (no bower in there). What I noticed: It only happens when the directory already is in place, therefore clearing the referenced cache works. It seems that it is neither a git:// vs. https:// or unauthenticated request nor a port issue. Btw, I run git version 1.7.9.5 just FYI. Hope this helps someone who stumbles upon it.

Edit: For later readers: Make sure you are providing credentials when using git:// or git@ pointers. Also check your SSH keys.

@saurabh-agrawal83

This comment has been minimized.

Show comment
Hide comment
@saurabh-agrawal83

saurabh-agrawal83 May 30, 2014

@jcumminsr1 - thanks for the tip. git config worked for me

git config --global url."https://".insteadOf git://

saurabh-agrawal83 commented May 30, 2014

@jcumminsr1 - thanks for the tip. git config worked for me

git config --global url."https://".insteadOf git://

@andreblumenau

This comment has been minimized.

Show comment
Hide comment
@andreblumenau

andreblumenau Aug 21, 2014

@jcumminsr1 - thanks for the tip. git config worked for me[2]

andreblumenau commented Aug 21, 2014

@jcumminsr1 - thanks for the tip. git config worked for me[2]

@TormodHystad

This comment has been minimized.

Show comment
Hide comment
@TormodHystad

TormodHystad Jan 19, 2015

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)

TormodHystad commented Jan 19, 2015

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)

@AntonMaltsev

This comment has been minimized.

Show comment
Hide comment
@AntonMaltsev

AntonMaltsev Mar 27, 2015

Thanks! Tip below helped! BTW not only on Mac, I'm on Windows

#mac only
rm -rf ~/.bower

AntonMaltsev commented Mar 27, 2015

Thanks! Tip below helped! BTW not only on Mac, I'm on Windows

#mac only
rm -rf ~/.bower

@thiagocavaloti

This comment has been minimized.

Show comment
Hide comment
@thiagocavaloti

thiagocavaloti May 25, 2015

like @renjithvincent said, git config --global url."https://".insteadOf git://
works for me too 👍

thiagocavaloti commented May 25, 2015

like @renjithvincent said, git config --global url."https://".insteadOf git://
works for me too 👍

@hjmodha

This comment has been minimized.

Show comment
Hide comment
@hjmodha

hjmodha Jun 8, 2015

thanks @renjithvincent, git config --global url."https://".insteadOf git:// worked for me

hjmodha commented Jun 8, 2015

thanks @renjithvincent, git config --global url."https://".insteadOf git:// worked for me

@chotkos

This comment has been minimized.

Show comment
Hide comment
@chotkos

chotkos Jul 7, 2015

Thanks, this helped me :)

chotkos commented Jul 7, 2015

Thanks, this helped me :)

@maboiteaspam

This comment has been minimized.

Show comment
Hide comment
@maboiteaspam

maboiteaspam Aug 3, 2015

faced the problem a moment ago,

bower -v 1.4.1

I was trying to install the module from a public github repo with
bower i maboiteaspam/grunt-vid2pict --save

Even i m the owner, i got
ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/maboiteaspam/grunt-vid2pic.git", exit code of #128 fatal: remote error: Repository not found.
(this cmd never worked for me, btw)

I had to change for explicit http
bower i https://github.com/maboiteaspam/grunt-vid2pict.git --save

The module would install.

I also tried bower cache clean before, but that did not help.

Maybe i did something wrong, only sharing.

maboiteaspam commented Aug 3, 2015

faced the problem a moment ago,

bower -v 1.4.1

I was trying to install the module from a public github repo with
bower i maboiteaspam/grunt-vid2pict --save

Even i m the owner, i got
ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/maboiteaspam/grunt-vid2pic.git", exit code of #128 fatal: remote error: Repository not found.
(this cmd never worked for me, btw)

I had to change for explicit http
bower i https://github.com/maboiteaspam/grunt-vid2pict.git --save

The module would install.

I also tried bower cache clean before, but that did not help.

Maybe i did something wrong, only sharing.

@esoyke

This comment has been minimized.

Show comment
Hide comment
@esoyke

esoyke May 10, 2016

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.

esoyke commented May 10, 2016

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.

@vkjangra1209

This comment has been minimized.

Show comment
Hide comment
@vkjangra1209

vkjangra1209 Jun 1, 2016

git config --global url."https://".insteadOf git:// worked for me. thnx

vkjangra1209 commented Jun 1, 2016

git config --global url."https://".insteadOf git:// worked for me. thnx

@pik

This comment has been minimized.

Show comment
Hide comment
@pik

pik Jul 18, 2016

Same issue here, I'd like to note that e.g. git ls-remote git@github.com:User/a_private_repo.git resolves correctly even though the bower git ls-remote git://github.com/User/private_repo does not? Is this a git issue or the way bower is expanding the urls ?

pik commented Jul 18, 2016

Same issue here, I'd like to note that e.g. git ls-remote git@github.com:User/a_private_repo.git resolves correctly even though the bower git ls-remote git://github.com/User/private_repo does not? Is this a git issue or the way bower is expanding the urls ?

@venkatav

This comment has been minimized.

Show comment
Hide comment
@venkatav

venkatav Feb 23, 2017

after git config --global url."https://".insteadOf git:// this git push is not working for me.

venkatav commented Feb 23, 2017

after git config --global url."https://".insteadOf git:// this git push is not working for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment