I'm trying to follow along angular-material tutoriel http://www.angular-meteor.com/tutorials/whatsapp/ionic/bootstrapping using ionic.
When I tried to do bower install, I got the following error:
bower not-cached git://github.com/driftyco/ionic-bower.git#1.2.4
bower resolve git://github.com/driftyco/ionic-bower.git#1.2.4
bower ECMDERR Failed to execute "git ls-remote --tags --heads
git://github.com/driftyco/ionic-bower.git", exit code of #128 ssh: Could not resolve
hostname https: Name or service not known fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Additional error details:
ssh: Could not resolve hostname https: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
I found many questions here with the same problem, and I lot of them were solved by running
git config --global url."https://".insteadOf git://
But I tried it, and it didn't solve mine.
is there anyway to fix it? if not, is there anyway other than bower to do this?
The problem was with the .gitconfig file (located for me case in c:/users/my-account-name/ )
I just deleted these lines
[url "https:/"]
insteadOf = git://
[url "http://"]
insteadOf = git://
and it worked. I think in my case, I shouldn't have run the command
git config --global url."https://".insteadOf git://
Related
when i am trying to install the pod its showing errors. how to solve this?
Apples-MacBook-Pro:~ apple$ cd /Users/apple/Desktop/lkmmlkmk
Apples-MacBook-Pro:lkmmlkmk apple$ pod init [!] Existing Podfile found
in directory Apples-MacBook-Pro:lkmmlkmk apple$ pod install Setting up
CocoaPods master repo fatal: ambiguous argument 'HEAD': unknown
revision or path not in the working tree. Use '--' to separate paths
from revisions, like this: 'git [...] --
[...]' fatal: ambiguous argument 'HEAD': unknown revision or
path not in the working tree. Use '--' to separate paths from
revisions, like this: 'git [...] -- [...]'
fatal: ambiguous argument 'HEAD': unknown revision or path not in the
working tree. Use '--' to separate paths from revisions, like this:
'git [...] -- [...]' $ /usr/bin/git -C
/Users/apple/.cocoapods/repos/master fetch origin --progress fatal:
'origin' does not appear to be a git repository fatal: Could not
read from remote repository.
Please make sure you have the correct access rights and the
repository exists. [!] Unable to add a source with url
https://github.com/CocoaPods/Specs.git named master-1. You can try
adding it manually in ~/.cocoapods/repos or via pod repo add.
This problem got solve by re setting the git manually if anyone having same issue just reset the cocoa-pods it will help you.
Go to ~/.cocoapods/repos and run git clone https://github.com/CocoaPods/Specs.git master
it will help you to resolve the solution
I have problem of installing angular translate local storage using "bower install angular-translate-storage-local --save-dev" in mac terminal. It just shows this error 'ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/^1/2.git", exit code of #128'.
Please help. I have tried 'git config --global url."https://".insteadOf git://' but it still does not work.
Note: I use bower version 1.7.9.
git config --global url."https://".insteadOf git://
I hope this will solve your problem. Please refer below same git issue.
https://github.com/Hacklone/private-bower/issues/102
I am trying to register a package using bower register <name> https://git#bitbucket.org.. but bower is not creating a new package and throwing error as it is not a valid url and URl has to start with git://. But in bitbucket they have given Url with https:// and git#bitbucket.org.
I have kept trying with https:// for registering the package but still problem persits. It is not allowing to register the package inside the bower.
So I need some help on creating package in bower with bitbucket repository so i hope someone would have done it. Thanks for your help!
try to config git global and try
git config --global url."https://".insteadOf git://
bower register <name>
i get this error while using bundle install in ROR.
Fetching git://github.com/pengwynn/linkedin.git
fatal: Unable to look up github.com (port 9418) (No such host is known. )
Git error: command git clone "git://github.com/pengwynn/linkedin.git" "C:/RailsInstaller/Ruby1.8.7/lib/ruby/gems/1.8/ca
che/bundler/git/linkedin-3e3919d62b37a1f8879ade6b51b3eeb032fc8973" --bare --no-hardlinks in directory C:/linkedin/linke
dinfrongit has failed.
I am using windows.
Are you behind a firewall blocking connections on port 9418? Perhaps you can give it a try with the http protocol?
git clone https://github.com/pengwynn/linkedin.git
Set proxy using git config command in the command prompt with
the following two commands:
git config --global http.proxy http://username:password#host:port
git config --global https.proxy http://username:password#host:port
In command like:
git clone git://github.com/saasbook/hw2_rottenpotatoes.git
Replace replace git:// with https://.
git clone https://github.com/saasbook/hw2_rottenpotatoes.git
I have tryed to run this code in my console:
script/plugin install git://github.com/apotonick/cells.git
...but i only get an empty folder named "cells" in my "vendor/plugins" dir.
What's wrong?
Check you Git version.
This may be related with you gitconfig file, as described in this thread
The reason is that it appears rails-2.3.5/lib/commands/plugin.rb is trying use git pull to grab the plugin code (see the install_using_git method), which doesn't work right.
Example:
script/plugin install git://github.com/fesplugas/typus.git
mkdir vendor/plugins/typus
cd vendor/plugins/typus
git init
git pull --depth 1 git://github.com/fesplugas/typus.git
That last line exits 1, but that error is being masked by the install_using_git method, and the directory is just rm -rf'ed.
I tracked this down to a conflict with ~/.gitconfig. If I remove these lines it works:
[branch "master"]
remote = origin
merge = refs/heads/master
It appears a naked git pull has problems with these settings.
Actually, the problem would be here because of a global git config file (in your homedir: '~/.gitconfig'), defining a master which may be incompatible with the master expected by the git pull within that specific Git repo.