Re: inted problems when upgrading to 1.6.0.4
- From
- Luis Gutierrez <luis.gutierrez@xmos.com>
- Date
- Nov 25, 2008, 10:54 UTC
- Message-ID
- <492BD951.1010200@xmos.com>
- In-Reply-To
- <1227610459.3222.4.camel@therock.nsw.bigpond.net.au>
Arafangion wrote:
Show 37 quoted lines
> On Tue, 2008-11-25 at 10:12 +0000, Luis Gutierrez wrote: > >> Arafangion wrote: >> >>> On Tue, 2008-11-25 at 09:29 +0000, Luis Gutierrez wrote: >>> <snip> >>> >>> >>>> All push/pull/clone operations were failing with the dreaded 'fatal: The >>>> remote end hung up unexpectedly'. After a few tests, this is what I found: >>>> >>>> - I can clone/pull/push if I do it through ssh (ie, git clone >>>> ssh://server/project) >>>> - I can clone/pull/push if I start git daemon on the command line through >>>> git daemon --syslog --verbose --export-all >>>> --base-path=/vol0/git/projects --verbose --reuseaddr >>>> >>>> But the way I had setup git, through xinetd is broken. >>>> >>>> >>> I'm just guessing, as I'm too new to the git world to respond with more >>> expertise, but I will suggest that perhaps your problem is that your >>> $PATH is different with the xinitd configuration as contrasted with your >>> ssh configuration, as the locations of the git binaries could be >>> different. >>> >>> >>> >> I've tried that, they are the same: >> >> # which git >> /usr/local/bin/git >> > > What about the other git-* commands? > >
This is what I have now: ls /usr/local/bin/git* git git-cvsserver gitk git-receive-pack git-shell git-upload-archive git-upload-pack it seems.. a lot less than it used to be, but then again, perhaps this is why the git-* commands were deprecated?
-- * Luis Gutierrez | * XMOS Semiconductor <http://www.xmos.com> Venturers House, King Street, Bristol BS1 4PB, UK