El OP skipper3kreports un problema con RUNTIME_PREFIX en Git, un poco similar a "git pull broken" pregunta:
I'm not sure whether RUNTIME_PREFIX is defined for you. But while nosing in the Makefile , I did notice that prefix defaults to $(HOME) . I suspect that this may be the cause of your problems.
The simple answer is to put this in ~/.bashrc :
export GIT_EXEC_PATH=/opt/local/libexec/git-core
If you want to find out more about what's going on, you'll probably have to recompile git using port -d upgrade -f git-core (or similar) and look closely at the build log to see where prefix is being set.
Incidentally, port cat git-core shows heavy usage of ${prefix} .
Respuesta original:
En primer lugar, circunstancias surgió la versión más actualizada gitolite al día?
En https://github.com/sitaramc/gitolite/, debe considerar la rama 'pu'.
El installation documentation is then this one.
GitoliteV3 or 'g3' doc:
"Installation" consists of the following options:
- Keep the sources anywhere and use the full path to run the gitolite command.
- Keep the sources anywhere and symlink just the gitolite program to some directory on your $PATH.
- Copy the sources somewhere and use that path to run the gitolite command.
You can run the 'install' command in 3 different ways:
# option 1
gitolite/install
# option 2
gitolite/install -ln
# defaults to $HOME/bin, or use a specific directory:
gitolite/install -ln /usr/local/bin
# option 3
gitolite/install -to /usr/local/gitolite/bin
vieja respuesta de gitolite V2: En segundo lugar, yo prefiero el método "from-client method":
The advantage of this method is that it forces you to solve the ssh pubkey problem before attempting to install.
It works best if you have dedicated userids,
- one on the server for installing gitolite,
- and one on the client for administering it.
The disadvantage is that the admin user ends up with two keys
- one for shell access (that he started with) and
- one for gitolite access (which the script creates if needed).
Así que me gustaría crear un archivo ~/.ssh/config con los dos conjuntos diferentes de parámetros:
host gitolite
user git
hostname server
identityfile ~/.ssh/git
host gitadmin
user git
hostname server
identityfile ~/.ssh/id_rsa (myaccount public key)
El gitolite-admin sólo es visible por primera clave pública SSH:
C:\HOMEWARE\git>ssh gitolite
hello git, the gitolite version here is v1.5.9-25-ga10287a
the gitolite config gives you the following access:
R W gitolite-admin
@R_ @W_ testing
Connection to server closed.
Con mi cuenta:
C:\HOMEWARE\git>ssh gitadmin
hello myaccount, the gitolite version here is v1.5.9-25-ga10287a
the gitolite config gives you the following access:
@R_ @W_ testing
Connection to mccprdgit10 closed.
Así:
C:\HOMEWARE\git>git clone gitolite:gitolite-admin
Cloning into gitolite-admin...
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 16 (delta 2), reused 0 (delta 0)
Receiving objects: 100% (16/16), done.
Resolving deltas: 100% (2/2), done.
lo que es el comando git clone utiliza? – VonC
git clone git @ server: gitolite-admin – skipper3k
Intentaría clonar de esta manera: "git clone ssh: // git @ server/gitolie-admin", pero no sé si esta es la causa de su problema. –