Erroneous git repository path in npm

[apricat]

Hi! We are having issues with our Jasmine Ajax installation since December. On npm install, we get git errors where git://github.com/pivotal/jasmine-ajax is called.

npm install

npm WARN `git config --get remote.origin.url` returned wrong result (git://github.com/pivotal/jasmine-ajax) undefined 
npm WARN `git config --get remote.origin.url` returned wrong result (git://github.com/pivotal/jasmine-ajax) undefined 
npm ERR! git clone git://github.com/pivotal/jasmine-ajax undefined 
npm ERR! git clone git://github.com/pivotal/jasmine-ajax undefined 
npm ERR! Failed using git.

git://github.com/pivotal/jasmine-ajax seems to now redirect to git://github.com/jasmine/jasmine-ajax.

This results in us getting the following error when attempting to run Karma tests:

Error: No provider for "framework:jasmine-ajax"! (Resolving: framework:jasmine-ajax)

Thank you!

[mentatxx]

I have got same issue here. I have installed karma-jasmine-ajax with --save-dev option

"jasmine-ajax": "~3.0.0",
"karma": "~0.12.31",
"karma-jasmine-ajax": "~0.1.4"

all dependencies are installed, but when i try to load framework, it failes find it:

frameworks: ['jasmine-ajax', 'jasmine', 'requirejs'],

Currently i have no idea why it happens, jasmine anf requires frameworks are loaded ok

Error: No provider for "framework:jasmine-ajax"! (Resolving: framework:jasmine-ajax)

[hasentopf]

npm ERR! git clone git://github.com/pivotal/jasmine-ajax Cloning into bare repository '/Users/mathias/.npm/_git-remotes/git-github-com-pivotal-jasmine-ajax-8282d883'...
npm ERR! git clone git://github.com/pivotal/jasmine-ajax 
npm ERR! git clone git://github.com/pivotal/jasmine-ajax fatal: unable to connect to github.com:
npm ERR! git clone git://github.com/pivotal/jasmine-ajax github.com[0: 192.30.252.129]: errno=Operation timed out

Same issue. The redirect from github.com/pivotal/jasmine-ajax to github.com/jasmine/jasmine-ajax seems to have issues. I work with:

    "karma": "0.12.28",
    "karma-jasmine": "0.3.2",

[pdeegan]

Please see #9 and #10 to see if this recent merge fixes your issue. Otherwise, I'm happy to merge pull requests. Thanks!