If you have a problem cloning a repository, or using it once it has been created, check the following:
- Ensure that the user has gone through initial
GitCentric login and has the correct
username,
email, and
ssh.
- Test the ssh configuration with this command:
ssh -p 29418 <gc_user>@<gitCentricServer> gitcentric --help
This should return a usage message that refers to the
config-branch,
config-repo, and
ls-repo commands. If the command returns an error message, ssh has not been set up correctly. In this case, try the command again
using a
-v switch to obtain additional messages that might be useful for debugging.
- Make sure that the path in the
git clone call is correct.
- If you have an authorization error, have an administrator check the ACLs in
.
- Have an administrator check the bare repo in the
GitCentric storage directory. Use commands such as
git log,
git branch, and
git cat-file –p master. If it is empty, check the log files for initial import/export failure.
Note: Git does not track empty directories although
AccuRev does. Therefore, if you have empty directories in your
AccuRev stream, these will NOT appear in a
Git clone of a repository that is mapped to that
AccuRev stream.