gitolite安装问题 [英] gitolite installation issue
本文介绍了gitolite安装问题的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
有没有人试过gitolite的easy install选项？
我想从我的windows（工作站）安装gitolite到solaris盒子。
[用于安装的命令]
./gl-easy-install -q git sjcfsap1 git
命令在以下位置中断。
* Y * ou是登录到系统：[gitserver]
克隆gitolite-admin repo ...
在c：/ Documents and Settings / chandve / gitolite-a
中初始化的空Git存储库dmin / .git /
密码：
致命：'gitolite-admin'似乎不是git存储库
致命：远程端意外挂起**
有没有人遇到过这个问题？
您认为gitolite值得这个努力吗？我期待为Git评估ACL。
感谢您提前给予回复。
[下面的完整命令执行日志]
CHANDVE @ CHANDVE / c / git / repos / gitolite / src ）
$ ./gl-easy-install git sjcfsap1 git
---------------------- --------------------------------------------------
您正在升级v1.5.3-13-g20c2e1a到v1.5.3-13-g20c2e1a
注意：只有'from'版本的'（未知）'应该只有发生一次。
为'to'版本获取'（未知）'意味着您可能从tar文件转储中安装
，而不是真正的克隆。这不是一个错误，但是如果您需要支持，
有这些版本号很好。尝试并从
克隆安装
...按回车键继续或按Ctrl-C键退出
- -------------------------------------------------- --------------------
下一个命令将为您的gitolite访问创建一个新的密钥对
pubkey将是/ c / Documents and Settings / chandve / .ssh / git.pub。您将获得
e选择一个
密码或者不输入。我建议现在不要使用
的密码，*尤其是*如果您没有密码，您已经使用
密钥来获取服务器访问权限！
在完成所有设置后，使用'ssh-keygen -p'添加一个，并且您
已成功克隆并推送gitolite-admin回购。之后，安装
'keychain'或类似的东西，并将以下命令添加到您的bashrc
中（因为这是一个非默认的键）
ssh-add $ HOME /.ssh/git
这使得使用密码短语非常方便。
...按回车键继续或按Ctrl-C键退出
------------ -------------------------------------------------- ----------
嗯... pubkey / c / Documents and Settings / chandve / .ssh / git.pub exists;我应该重新使用它吗？
重要提示：安装完成后，* this *键不能再用于获取服务器上的
a命令行 - 它将被gitolite使用，用于git访问$ b $只有b。如果这是一个问题，请立即停止。
doc / 6-ssh-troubleshooting.mkd将解释这里发生的事情，如果您需要
更多信息。
...按回车键继续或按Ctrl-C键退出
------------ -------------------------------------------------- ----------
您的$ HOME / .ssh / config已经设置了gitolite。我会假设
它们是正确的，但如果它们不正确，请编辑该文件，删除
段落（该行和下面几行），Ctrl-C并重新运行。
如果你想立即检查（从另一个终端），如果他们是
正确的，下面是他们*应该*看起来像：
主机gitolite
用户git
主机名sjcfsap1
端口22
身份文件〜/ .ssh / git
...按enter键继续或Ctrl-C保存
gitolite.pm 100％26KB 26.3KB / s 00:00
gl-auth-command 100％8319 8.1KB / s 00:00
gl-compile-conf 100％26KB 25.6KB / s 00:00
gl-conf-convert 100％2325 2.3KB / s 00:00
gl-easy-install 100％23KB 23.2KB / s 00:00
gl-emergency-addkey 100％1295 1.3KB / s 00:00
gl-install 100％4087 4.0KB / s 00:00
gl-setup 100％3081 3.0KB / s 00:00
gl-sy干安装100％1814 1.8KB / s 00:00
gl-tool 100％2145 2.1KB / s 00:00
output.txt 100％60KB 60.2KB / s 00:00
sshkeys-lint 100％2962 2.9KB / s 00:00
example.conf 100％12KB 12.1KB / s 00:00
example.gitolite.rc 100％8390 8.2KB / s 00:00
VERSION 100％19 0.0KB / s 00:00
0-INSTALL.mkd 100％12KB 11.6KB / s 00:00
1-migrate.mkd 100％3569 3.5KB / s 00:00
2-admin.mkd 100％9063 8.9KB / s 00:00
3-faq-tips-etc.mkd 100％29KB 29.0KB / s 00:00
4 -wildcard-repositories.mkd 100％12KB 11.8KB / s 00:00
5-delegation.mkd 100％6143 6.0KB / s 00:00
6-ssh-troubleshooting.mkd 100％19KB 19.5KB / s 00:00
7-install-transcript.mkd 100％8372 8.2KB / s 00 ：00
9-gitolite-and-ssh.mkd 100％7798 7.6KB / s 00:00
9-packaging.mkd 100％2257 2.2KB / s 00:00
9- uninstall.mkd 100％2791 2.7KB / s 00:00
admin-defined-commands.mkd 100％9700 9.5KB / s 00:00
big-config.mkd 100％6469 6.3KB / s 00:00
CHANGELOG 100％3873 3.8KB / s 00:00
复制100％18KB 17.9KB / s 00:00
hook-propagation.mkd 100％7654 7.5KB / s 00 ：00
overkill.mkd 100％2059 2.0KB / s 00:00
progit-article.mkd 100％12KB 12 .5KB / s 00:00
report-output.mkd 100％1818 1.8KB / s 00:00
shell-games.mkd 100％3363 3.3KB / s 00:00
gitolite -hooked 100％0 0.0KB / s 00:00
更新100％4728 4.6KB / s 00:00
更新后100％943 0.9KB / s 00:00
-------------------------------------------- ----------------------------
gitolite rc文件需要手工编辑。默认值是合理的，
，所以如果你愿意，你可以退出编辑器。
否则，请进行任何更改并保存。阅读注释
了解什么是 - rc文件的文档是内联的。
请记住这个文件实际上会被复制到服务器上，并且所有
路径等代表服务器上的路径！
...按回车键继续或按Ctrl-C键退出
------------ -------------------------------------------------- ----------
哦，嘿，你已经在服务器上有一个'.gitolite.rc'文件。
让我们看看我们是否可以使用它，而不是默认的...
...按enter键继续或按Ctrl-C键退出
.gitolite.rc 100 ％8390 8.2KB / s 00:00
----------------------------- -------------------------------------------
忽略
下一组命令输出中的任何'请编辑此文件'或'运行此命令'类型的行。它们只与手动
安装有关，而不是这一个...
...按enter键继续或按Ctrl-C键退出
***警告***：看起来像升级...忽略参数'git'
/ export / home / git / repositories已存在
/ export / home / git /。 gitolite已存在
/export/home/git/.gitolite/conf已存在
/export/home/git/.gitolite/doc已存在
/export/home/git/.gitolite / keydir已存在
/export/home/git/.gitolite/logs已存在
/export/home/git/.gitolite/src已存在
/ export / home / git /。 gitolite / hooks已存在
/export/home/git/.gitolite/hooks/common已存在
/export/home/git/.gitolite/hooks/gitolite-admin已存在
复制post-update hook到gitolite-admin repo ...
伪终端不会被分配，因为stdin不是终端。
stty ::无效参数
您正在登录系统：sjcfsap1
/ export / home / git / repositories已存在
/export/home/git/.gitolite已存在
/export/home/git/.gitolite/conf已存在
/export/home/git/.gitolite/doc已存在
/ export / home / git / .gitolite / keydir已存在
/export/home/git/.gitolite/logs已存在
/export/home/git/.gitolite/src已存在
/export/home/git/.gitolite/hooks已存在
/export/home/git/.gitolite/hooks/common已存在
/export/home/git/.gitolite/hooks/gitolite- admin已存在
复制post-update钩子到gitolite-admin repo ...
------------------ -------------------------------------------------- ----
现在我们将gitolite-admin repo克隆到您的工作站，并查看它是否
全部挂在一起。我们现在将在您的$ HOME中执行此操作，如果您愿意，您可以稍后在其他位置移动
。
...按回车继续或Ctrl-C保存
在c：/ Documents and Settings / chandve / gitolite-a $ b $中初始化的空的Git仓库b dmin / .git /
密码：
密码：
致命：'gitolite-admin'似乎不是git存储库
致命：远程端意外挂起
解决方案
如果在服务器上 git 用户在〜/ .ssh / authorized_keys 中有一个用于远程用户的密钥，该用户没有加上命令变量：
％cat〜/ .ssh / authorized_keys
ssh-rsa ...... user @ host
＃gitolite start
command =/ home / gituser / .... user @ host
＃gitolite end
％
只要删除第一行，您就可以轻松前往。
Has any one tryied the easy install option of gitolite?
I am trying to install gitolite from my windows (workstation ) to a solaris box.
[command used to install]
./gl-easy-install -q git sjcfsap1 git
The command breaks at the following place .
*Y*ou are logging into system : [gitserver]
cloning gitolite-admin repo...
Initialized empty Git repository in c:/Documents and Settings/chandve/gitolite-a
dmin/.git/
Password:
fatal: 'gitolite-admin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly**
Has any one encountered this issue? Do you think gitolite is worth this effort? I am looking to evaluate ACL for Git.
Thanks for your response in advance.
[The complete command execution log below]
CHANDVE@CHANDVE /c/git/repos/gitolite/src (master)
$ ./gl-easy-install git sjcfsap1 git
------------------------------------------------------------------------
you are upgrading v1.5.3-13-g20c2e1a to v1.5.3-13-g20c2e1a
Note: getting '(unknown)' for the 'from' version should only happen once.
Getting '(unknown)' for the 'to' version means you are probably installing
from a tar file dump, not a real clone. This is not an error but it's nice to
have those version numbers in case you need support. Try and install from a
clone
...press enter to continue or Ctrl-C to bail out
------------------------------------------------------------------------
the next command will create a new keypair for your gitolite access
The pubkey will be /c/Documents and Settings/chandve/.ssh/git.pub. You will hav
e to choose a
passphrase or hit enter for none. I recommend not having a passphrase for
now, *especially* if you do not have a passphrase for the key which you are
already using to get server access!
Add one using 'ssh-keygen -p' after all the setup is done and you've
successfully cloned and pushed the gitolite-admin repo. After that, install
'keychain' or something similar, and add the following command to your bashrc
(since this is a non-default key)
ssh-add $HOME/.ssh/git
This makes using passphrases very convenient.
...press enter to continue or Ctrl-C to bail out
------------------------------------------------------------------------
Hmmm... pubkey /c/Documents and Settings/chandve/.ssh/git.pub exists; should I j
ust (re-)use it?
IMPORTANT: once the install completes, *this* key can no longer be used to get
a command line on the server -- it will be used by gitolite, for git access
only. If that is a problem, please ABORT now.
doc/6-ssh-troubleshooting.mkd will explain what is happening here, if you need
more info.
...press enter to continue or Ctrl-C to bail out
------------------------------------------------------------------------
your $HOME/.ssh/config already has settings for gitolite. I will assume
they're correct, but if they're not, please edit that file, delete that
paragraph (that line and the following few lines), Ctrl-C, and rerun.
In case you want to check right now (from another terminal) if they're
correct, here's what they are *supposed* to look like:
host gitolite
user git
hostname sjcfsap1
port 22
identityfile ~/.ssh/git
...press enter to continue or Ctrl-C to bail out
gitolite.pm 100% 26KB 26.3KB/s 00:00
gl-auth-command 100% 8319 8.1KB/s 00:00
gl-compile-conf 100% 26KB 25.6KB/s 00:00
gl-conf-convert 100% 2325 2.3KB/s 00:00
gl-easy-install 100% 23KB 23.2KB/s 00:00
gl-emergency-addkey 100% 1295 1.3KB/s 00:00
gl-install 100% 4087 4.0KB/s 00:00
gl-setup 100% 3081 3.0KB/s 00:00
gl-system-install 100% 1814 1.8KB/s 00:00
gl-tool 100% 2145 2.1KB/s 00:00
output.txt 100% 60KB 60.2KB/s 00:00
sshkeys-lint 100% 2962 2.9KB/s 00:00
example.conf 100% 12KB 12.1KB/s 00:00
example.gitolite.rc 100% 8390 8.2KB/s 00:00
VERSION 100% 19 0.0KB/s 00:00
0-INSTALL.mkd 100% 12KB 11.6KB/s 00:00
1-migrate.mkd 100% 3569 3.5KB/s 00:00
2-admin.mkd 100% 9063 8.9KB/s 00:00
3-faq-tips-etc.mkd 100% 29KB 29.0KB/s 00:00
4-wildcard-repositories.mkd 100% 12KB 11.8KB/s 00:00
5-delegation.mkd 100% 6143 6.0KB/s 00:00
6-ssh-troubleshooting.mkd 100% 19KB 19.5KB/s 00:00
7-install-transcript.mkd 100% 8372 8.2KB/s 00:00
9-gitolite-and-ssh.mkd 100% 7798 7.6KB/s 00:00
9-packaging.mkd 100% 2257 2.2KB/s 00:00
9-uninstall.mkd 100% 2791 2.7KB/s 00:00
admin-defined-commands.mkd 100% 9700 9.5KB/s 00:00
big-config.mkd 100% 6469 6.3KB/s 00:00
CHANGELOG 100% 3873 3.8KB/s 00:00
COPYING 100% 18KB 17.9KB/s 00:00
hook-propagation.mkd 100% 7654 7.5KB/s 00:00
overkill.mkd 100% 2059 2.0KB/s 00:00
progit-article.mkd 100% 12KB 12.5KB/s 00:00
report-output.mkd 100% 1818 1.8KB/s 00:00
shell-games.mkd 100% 3363 3.3KB/s 00:00
gitolite-hooked 100% 0 0.0KB/s 00:00
update 100% 4728 4.6KB/s 00:00
post-update 100% 943 0.9KB/s 00:00
------------------------------------------------------------------------
the gitolite rc file needs to be edited by hand. The defaults are sensible,
so if you wish, you can just exit the editor.
Otherwise, make any changes you wish and save it. Read the comments to
understand what is what -- the rc file's documentation is inline.
Please remember this file will actually be copied to the server, and that all
the paths etc. represent paths on the server!
...press enter to continue or Ctrl-C to bail out
------------------------------------------------------------------------
Oh hey... you already had a '.gitolite.rc' file on the server.
Let's see if we can use that instead of the default one...
...press enter to continue or Ctrl-C to bail out
.gitolite.rc 100% 8390 8.2KB/s 00:00
------------------------------------------------------------------------
ignore any 'please edit this file' or 'run this command' type lines in the
next set of command outputs coming up. They're only relevant for a manual
install, not this one...
...press enter to continue or Ctrl-C to bail out
*** WARNING ***: looks like an upgrade... ignoring argument 'git'
/export/home/git/repositories already exists
/export/home/git/.gitolite already exists
/export/home/git/.gitolite/conf already exists
/export/home/git/.gitolite/doc already exists
/export/home/git/.gitolite/keydir already exists
/export/home/git/.gitolite/logs already exists
/export/home/git/.gitolite/src already exists
/export/home/git/.gitolite/hooks already exists
/export/home/git/.gitolite/hooks/common already exists
/export/home/git/.gitolite/hooks/gitolite-admin already exists
copying post-update hook to gitolite-admin repo...
Pseudo-terminal will not be allocated because stdin is not a terminal.
stty: : Invalid argument
You are logging into system : sjcfsap1
/export/home/git/repositories already exists
/export/home/git/.gitolite already exists
/export/home/git/.gitolite/conf already exists
/export/home/git/.gitolite/doc already exists
/export/home/git/.gitolite/keydir already exists
/export/home/git/.gitolite/logs already exists
/export/home/git/.gitolite/src already exists
/export/home/git/.gitolite/hooks already exists
/export/home/git/.gitolite/hooks/common already exists
/export/home/git/.gitolite/hooks/gitolite-admin already exists
copying post-update hook to gitolite-admin repo...
------------------------------------------------------------------------
now we will clone the gitolite-admin repo to your workstation and see if it
all hangs together. We'll do this in your $HOME for now, and you can move
it elsewhere later if you wish to.
...press enter to continue or Ctrl-C to bail out
Initialized empty Git repository in c:/Documents and Settings/chandve/gitolite-a
dmin/.git/
Password:
Password:
fatal: 'gitolite-admin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
解决方案
This can occur if on the server, the git user has a key in ~/.ssh/authorized_keys for the remote user that is not prefixed with the command variable:
% cat ~/.ssh/authorized_keys
ssh-rsa ...... user@host
# gitolite start
command="/home/gituser/.... user@host
# gitolite end
%
Just remove the first line and you're good to go.
这篇关于gitolite安装问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
