Issues with new install
James S
greatly appreciate any help on a solution. I'm running version 1.3
pulled from github. I'm running git 1.7.2 on the server. Git version
on the client is 1.6.4.2.
First, I realize that new repos that are made are bare. I've setup
what I believe is the correct remote config to run the following
command: git push origin master
I get the following results:
Counting objects: 3, done.
Writing objects: 100% (3/3), 211 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Use of uninitialized value in do "file" at hooks/update line 32.
Null filename used at hooks/update line 32.
error: hook declined to update refs/heads/master
To g...@xxx.net:~/repositories/testing.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'g...@xxx.net:~/repositories/
testing.git'
First, the mention of an error on hooks/update line 32. Not sure what
thats about, but I assume that's why this push fails.
You may of also noticed that I'm using ~/repositories/ to path to the
repos. I'm not sure why I have to do that, but if I don't it complains
the repo isn't found. Maybe something related to that is messing
things up...
Also odd is that many git commands end with the error: "fatal: The
remote end hung up unexpectedly" Watching the /var/log/secure shows a
successful key login to user git.
It's possible these are all related in some way which I just haven't
figured out yet. Line 32 of the hook is a comment, so I'm obviously
missing something there as well...
Any help would be great, because I'm losing some hair over something
that was supposed to save me hair.
Cheers and Thanks,
James
Teemu Matilainen
> You may of also noticed that I'm using ~/repositories/ to path to the
> repos. I'm not sure why I have to do that, but if I don't it complains
> the repo isn't found. Maybe something related to that is messing
> things up...
Sitaram for sure gives the right diagnostic when he wakes up. =)
But it seems that you are bypassing the gitolite totally. Probably the
key that you use is declared in ~/.ssh/authorized_keys on the server
before the '# gitolite start' line.
See doc/6-ssh-troubleshooting.mkd for more help:
http://github.com/sitaramc/gitolite/blob/pu/doc/6-ssh-troubleshooting.mkd
Cheers,
- Teemu
Sitaram Chamarty
<teemu.ma...@iki.fi> wrote:
> On Tue, 06 Apr 2010, James S wrote:
>
>> You may of also noticed that I'm using ~/repositories/ to path to the
>> repos. I'm not sure why I have to do that, but if I don't it complains
>> the repo isn't found. Maybe something related to that is messing
>> things up...
>
> Sitaram for sure gives the right diagnostic when he wakes up. =)
More correct than what you gave already? No... :)
> But it seems that you are bypassing the gitolite totally. Probably the
Indeed... You are definitely accessing the repo using a non-gitolite
key (a key which does not have "command=..." restriction in t he
authkeys file.
> key that you use is declared in ~/.ssh/authorized_keys on the server
> before the '# gitolite start' line.
>
> See doc/6-ssh-troubleshooting.mkd for more help:
> http://github.com/sitaramc/gitolite/blob/pu/doc/6-ssh-troubleshooting.mkd
After reading that link, also please run the sshkeys-lint program
which is in src/ (run it without arguments to see usage). It will
help you track down what is happening.
Regards,
Sitaram
Sitaram Chamarty
> remote: error: hook declined to update refs/heads/master To git@server
> IP:repositories/gitolite-admin ! [remote rejected] master -> master (hook
> declined)
remove "repositories/" from the repo URL.
Of course then you will run up against a completely different error,
because you are (probably) using a wrong key. Start at
http://sitaramc.github.com/gitolite/ssh.html and read *everything*.
> On Wednesday, April 7, 2010 4:06:41 PM UTC+5:30, Sitaram Chamarty wrote:
As a rule, reviving a thread that is 2.5 years old is not going to
help much. There are some cases where it makes sense, but it is rare
and this is not one of them.