I am not sure why, but that ambertools-test repo was renamed to
ambertools-ci (
https://github.com/Amber-MD/ambertools-ci)
Can you try git clone that repo directly to see if you got the denial?
I will have a look tonight.
Meanwhile, you can safely ignore that repo to continue your work.
Hai
On Mon, Jun 12, 2017 at 11:08 AM, David Cerutti <dscerutti.gmail.com> wrote:
> Hello devs,
>
> Has anyone seen this problem? It looks like a git permissions issue, but
> that is very odd since I can do a clean
>
> git clone gitosis.git.ambermd.org:/amber.git <amber install directory>
>
> without problems. However, if I then do
>
> git pull
> git submodule update --init
>
> Submodule 'AmberTools/src/ambertools-binary-build' (
> https://github.com/Amber-MD/ambertools-binary-build) registered for path
> 'AmberTools/src/ambertools-binary-build'
> Submodule 'AmberTools/src/build-bot/ambertools-test'
> (git.github.com:Amber-MD/ambertools-test)
> registered for path 'AmberTools/src/build-bot/ambertools-test'
> Submodule 'AmberTools/src/build-bot/docker-amber-build-box'
> (git.github.com:Amber-MD/docker-amber-build-box)
> registered for path 'AmberTools/src/build-bot/docker-amber-build-box'
> Submodule 'AmberTools/src/cphstats' (git.github.com:/Amber-MD/
> cphstats.git)
> registered for path 'AmberTools/src/cphstats'
> Submodule 'AmberTools/src/cpptraj' (git.github.com:/Amber-MD/cpptraj.git)
> registered for path 'AmberTools/src/cpptraj'
> Submodule 'AmberTools/src/parmed' (git.github.com:/ParmEd/ParmEd.git)
> registered for path 'AmberTools/src/parmed'
> Submodule 'AmberTools/src/pdb4amber' (git.github.com:/Amber-MD/pdb4amber)
> registered for path 'AmberTools/src/pdb4amber'
> Submodule 'AmberTools/src/pytraj' (git.github.com:/Amber-MD/pytraj.git)
> registered for path 'AmberTools/src/pytraj'
> Cloning into 'AmberTools/src/ambertools-binary-build'...
> remote: Counting objects: 1700, done.
> remote: Compressing objects: 100% (71/71), done.
> remote: Total 1700 (delta 60), reused 65 (delta 32), pack-reused 1597
> Receiving objects: 100% (1700/1700), 246.98 KiB, done.
> Resolving deltas: 100% (1012/1012), done.
> Submodule path 'AmberTools/src/ambertools-binary-build': checked out
> '18c419831a106b836ed60bf2296c241a44a4714e'
> Cloning into 'AmberTools/src/build-bot/ambertools-test'...
> Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Clone of 'git.github.com:Amber-MD/ambertools-test' into submodule path
> 'AmberTools/src/build-bot/ambertools-test' failed
> [cerutti.casegroup1 amber3]$ ls AmberTools/src/build-bot/
>
> It looks like a permissions issue, but I'm not certain. The directory
> AmberTools/src/build-bot/ certainly exists, and I'm assuming that it wants
> to clone a new directory ambertools-test/ into that, but at present I don't
> see ambertools-test/. I've been trying to clone a new repo because I've
> been having this same problem when I try to update the current repo I've
> been working in. Am I missing something obvious?
>
> Thanks!
>
> Dave
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Mon Jun 12 2017 - 08:30:04 PDT
