On 2016-12-07 13:09, Paul-Erik Törrönen wrote:
On 2016-11-17 08:57, Jef Driesen wrote:
Yes, there is the mirror at sourceforge: git clone git://git.code.sf.net/p/libdivecomputer/code
There still is something off with the git.libdivecomputer.org-repo. If I do:
$ git clone git://git.libdivecomputer.org/libdivecomputer.git Cloning into 'libdivecomputer'... remote: Counting objects: 7881, done. remote: Compressing objects: 100% (2326/2326), done. remote: Total 7881 (delta 6319), reused 6864 (delta 5551) Receiving objects: 100% (7881/7881), 1.50 MiB | 969.00 KiB/s, done. Resolving deltas: 100% (6319/6319), done. Checking connectivity... done. warning: remote HEAD refers to nonexistent ref, unable to checkout.
$ cd libdivecomputer $ git checkout master error: pathspec 'master' did not match any file(s) known to git.
$ git ls-remote origin 4df5e490083fe235293d3c17903b48d56100775a refs/heads/release-0.1 ...
While the clone from Sourceforge says:
$ git ls-remote origin 296b13947f2f002929d60aaa29b1d686fc813d55 HEAD 296b13947f2f002929d60aaa29b1d686fc813d55 refs/heads/master 4df5e490083fe235293d3c17903b48d56100775a refs/heads/release-0.1 ...
I can confirm the problem. It looks like the HEAD and master refs are missing. The strange part is that I only see this problem with the git protocol, not with the ssh protocol. (And that's why I never noticed this myself.)
@Dirk: Can you check the server setup?
Should the Sourceforge be considered to be the primary source?
The git repository on libdivecomputer.org is the primary repository. But I keep the sourceforge repo in sync as a mirror. So unless there is something wrong with one of them, there shouldn't be any difference.
Jef