From: Raimund Bauer <ray007@gmx.net>
To: Andrew Ruder <andy@aeruder.net>
Cc: git@vger.kernel.org
Subject: Re: problem pushing repository
Date: Fri, 22 Jun 2007 09:21:56 +0200 [thread overview]
Message-ID: <1182496916.6207.11.camel@localhost> (raw)
In-Reply-To: <20070622022426.GA2961@bowser.ruder>
On Thu, 2007-06-21 at 21:24 -0500, Andrew Ruder wrote:
> On Thu, Jun 21, 2007 at 07:00:18PM -0700, Junio C Hamano wrote:
> > $ ssh newberry.ihepa.ufl.edu sh -c 'echo $PATH'
> >
> > may be a good starting point to test this, and the first step
> > to fix it would be
> >
> > $ man ssh
> > $ man sshd
>
> While I wholeheartedly agree with Junio here, you may also find
>
> remote.<name>.receivepack
Yes, but it doesn't always work.
I have a server with several repositories, and git is installed
in /usr/local/bin.
All my local repostories know this server as a remote named 'slcom' and
I have a 2 global options
remote.slcom.uploadpack=/usr/local/bin/git-upload-pack
remote.slcom.receivepack=/usr/local/bin/git-receive-pack
Fetching, pulling and normal pushing works.
Pushing a new branch to the remote doesn't work:
$ git branch test
$ git push slcom test:test
error: dst refspec test does not match any existing ref on the remote
and does not start with refs/.
fatal: The remote end hung up unexpectedly
error: failed to push to
'ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate'
git-remote also has a problem:
$ git remote show slcom
bash: git-upload-pack: command not found
fatal: The remote end hung up unexpectedly
ls-remote --heads
ray@softwarelandschaft.com:/home/ray/repos/drupal/multirate: command
returned error: 1
All this with git from yesterday (next).
> - Andy
--
best regards
Ray
next prev parent reply other threads:[~2007-06-22 7:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 1:49 problem pushing repository Adam Mercer
2007-06-22 2:00 ` Junio C Hamano
2007-06-22 2:24 ` Andrew Ruder
2007-06-22 7:21 ` Raimund Bauer [this message]
2007-06-22 11:26 ` Johannes Schindelin
2007-06-22 13:38 ` Raimund Bauer
2007-06-22 22:47 ` Shawn O. Pearce
2007-06-23 10:12 ` Raimund Bauer
2007-06-24 23:47 ` Shawn O. Pearce
2007-06-25 1:01 ` Jakub Narebski
2007-06-22 13:36 ` Adam Mercer
2007-06-22 14:17 ` Raimund Bauer
2007-06-22 14:32 ` Adam Mercer
2007-06-22 13:23 ` Adam Mercer
2007-06-22 7:20 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1182496916.6207.11.camel@localhost \
--to=ray007@gmx.net \
--cc=andy@aeruder.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.