On Mon, Apr 11, 2011 at 10:08 AM, git_usr <[email protected]> wrote:

> Thanks Marius,
>
> I inherited the project to get gitorious going from 'the last guy',
> but lucky enough have been able to contact him in the few mins since
> you posted that link (he's in same building) and asked how old the git
> clone he left me was.
> He now tells me it is from a branch modified to run gitorious from a
> suburi because our work dev server is http://<server-ip>/gitorious/
> not http://git.<server-ip>/
> From here:  https://gitorious.org/~tschamm
> I honestly thought he may be joking - is that a 'silent t' (no
> disrespect intended to the person) - but I've checked the repo and it
> appears active tho no sign there how to fix my error.
>
> Do you think this is the cause of the error - the suburi branch is out
> of date?
> I was the one that installed gitorious from the suburi clone left for
> me, so I could re-install from your mainline (which till now I thought
> our install was from), but would this work with the address we need:
> http://<server-ip>/gitorious/ ???


Ah, okay, that probably explains that the error message was not the same as
Gitorious would emit today. I think it would be a good idea to at least keep
the branch you're running from "alive" by rebasing the activities in
mainline onto the branch you're using, but that's probably not the problem
here.

A couple of things to have a look at:
- ~git/.ssh/authorized_keys should contain your public key along with your
username
- the ip address/hostname and port specified in config/gitorious.yml:
gitorious_client_host and gitorious_client_port should be accessible on the
server. Try running `curl -I
http://<gitorious_client_host>:<gitorious_client_port>/`
and verify that the server responds
- Have a look in the data/hooks directory of your Gitorious installation and
compare the scripts to what is in Gitorious' mainline.
- Make sure you have no custom hooks in the repository you're trying to push
from

Cheers,
- Marius

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to