Tuesday, May 20, 2014

shallow over http or ftp not supported

shallow over http or ftp not supported

Ever seen that?

Perhaps, the client version of git you're using and the https protocol running on your repo server are incompatible.

$ git clone --depth 1 https://github.com/visionmedia/git-extras.git
Initialized empty Git repository in /tmp/git-extras/.git/
shallow over http or ftp not supported


In any case, if you do see that error try down grading to the plain git protocol and try again

$ git clone --depth 1 git://github.com/visionmedia/git-extras.git
Initialized empty Git repository in /home/deploy/CHDataStructures/.git/
remote: Reusing existing pack: 5941, done.
remote: Counting objects: 145, done.
remote: Compressremote: ing objects: 100% (84/84), done.
remote: Total 6086 (delta 61), reused 123 (delta 46)
Receiving objects: 100% (6086/6086), 5.34 MiB | 3372 KiB/s, done.
Resolving deltas: 100% (3576/3576), done.


Git Protocols

Here's the list of current git protocols. Choose the most appropriate. ssh is typically recommended.

git

  • Example: git://repo_name/github.com/
  • basic, no security, server not verified
  • can pull, cannot push

http

  • Example: http://repo_name/github.com/
  • does not provide security, server not verified
  • not available on github.com

https

  • Example: https://repo_name/github.com/
  • server not verified via ssl certs
  • password auth for push, allows anonymous pull

ssh

  • Example: ssh://repo_name/github.com/
  • Example: git@repo_name/github.com:user_name/
  • You must generate an ssh keypair, then add it to your account
  • GitHub/Bitbucket account required


References

https://help.github.com/articles/generating-ssh-keys
https://confluence.atlassian.com/display/BITBUCKET/Use+the+SSH+protocol+with+Bitbucket

No comments:

Post a Comment