Configuring public key of users via gitolite throws error

I have added the public key of a user and pushed to the server.
But while running the gl-setup I have used like /tmp/ instead of /tmp/

Now I have altered the file name and then again tried to run the gl-setup.

  • How can I use two SVN projects and corresponding git-svn branches with a single working directory?
  • Github Line Comments in Task Navigation IDEA IntelliJ
  • How git-pull corporate with git-fetch (was: what does git-pull option `-p` mean)?
  • Can a project have multiple origins?
  • Can't clone git repo on windows when some file names contain asterisk
  • Eclipse hangs on “Re-indexing (fully) repository {username}”
  • It shows the message at last like this maps to user id_rsa, not rekha.
    You will not be able to access gitolite with this key.
    Look for the 'ssh troubleshooting' link in

    How to solve this problem?

  • Max file size and max repository size in Git?
  • Why `git show-ref FETCH_HEAD` is empty?
  • Adding a collaborator to my free GitHub account?
  • How to disconnect git for a project in intellij?
  • how to set google-chrome as git default browser
  • Issues while creating repository?
  • One Solution collect form web for “Configuring public key of users via gitolite throws error”

    First gl-setup is a gitolite V2 or ‘g2’ command.
    The current documentation for installation is for GitoliteV3 (or ‘g3’): an upgrade would be wise (for ease of support)

    Looking at the sources of gitolite, I find sshkeys-lint which will check for gitolite admin user:

    if ($admin) {
        my $fp = fprint("$");
        my $fpu = ( $seen_fprints{$fp}{user} || 'no access' );
        # dbg("fpu = $fpu, admin=$admin");
        die "\t\t*** FATAL ***\n" .
            "$ maps to $fpu, not $admin.\n" .
            "You will not be able to access gitolite with this key.\n" .
            "Look for the 'ssh troubleshooting' link in\n"
        if $fpu ne "user $admin";

    You might need to try again gl-setup, as explained by the ssh troubleshooting for g2.
    If that fails, check your ~gitolite-user-account/.ssh/authorized-keys and make sure id_rsa is replaced, if present, by rekha.

    The OP thillaiselvan reports in the comment having a working Gitolite again:

    I have achieved it by:

    • replacing deleting the id_rsa content in the authorized-keys file.
    • Created a fresh pub key for the rekha user.
    • And then freshly pushed it which is a huge work around.

    Now it works fine 🙂

    Git Baby is a git and github fan, let's start git clone.