From: John Keeping <john@keeping.me.uk>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Fred's Personal <freddiewik@optonline.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Trouble Cloning Git remote repository
Date: Mon, 29 Feb 2016 09:34:51 +0000 [thread overview]
Message-ID: <20160229093451.GC1766@serenity.lan> (raw)
In-Reply-To: <CACsJy8CSrmahLztOmmU+R4KTifhRs5nsSPKOdYHHw57UqDv8oQ@mail.gmail.com>
On Mon, Feb 29, 2016 at 08:20:46AM +0700, Duy Nguyen wrote:
> On Mon, Feb 29, 2016 at 12:48 AM, Fred's Personal
> <freddiewik@optonline.net> wrote:
> > Duy,
> >
> > Thanks for advice, here is the result of executing the lines you suggested:
> >
> > user1@Host1 MINGW64 ~/gitrepository (master)
> > $ export GIT_TRACE=1
> >
> > user1@Host1 MINGW64 ~/gitrepository (master)
> > $ git clone -v ssh://user1@Host2/srv/centralrepo
> > 12:33:47.928365 git.c:348 trace: built-in: git 'clone' '-v' 'ssh://user1@Host2/srv/centralrepo'
> > Cloning into 'centralrepo'...
> > 12:33:48.022110 run-command.c:343 trace: run_command: 'C:\Program Files (x86)\PuTTY\plink.exe' 'user1@Host2' 'git-upload-pack '\''/srv/centralrepo'\'''
>
> This command looks good to me. So I have no clue what goes wrong :-)
> Maybe you can execute this command directly, with more plink debugging
> options or something. You don't have to run git-upload-pack. Just
> spawn a shell. Another option is try something other than plink (does
> git-for-windows come with ssh.exe?)
On Windows it's probably going through mingw_spawnve_fd() which
reassembles a quoted command line from the individual arguments. It
would be interesting to see what gets passed to CreateProcessW().
> > ##>>>Lines from $HOME/.bashrc (See below, removed here for clarity)
> >
> > + user1@Host2 git-upload-pack /srv/centralrepo
> > bash: user1@Host2: command not found
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
> >
> >
> > Regards,
> > Fred
> >
> > freddiewik@optonline.net
> >
> >
> > -----Original Message-----
> > From: Duy Nguyen [mailto:pclouds@gmail.com]
> > Sent: Saturday, February 27, 2016 4:36 AM
> > To: Fred's Personal
> > Cc: Git Mailing List
> > Subject: Re: Trouble Cloning Git remote repository
> >
> > On Sat, Feb 27, 2016 at 6:03 AM, Fred's Personal <freddiewik@optonline.net> wrote:
> >> $ git clone -v ssh://user1@Host2/srv/centralrepo Cloning into
> >> 'centralrepo'...
> >>>>>Lines from $HOME/.bashrc
> >> + export
> >> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr
> >> /games
> >> :/usr/local/games
> >> +
> >> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr
> >> /games
> >> :/usr/local/games
> >> + PROMPT_COMMAND=
> >> + CDPATH=
> >> + '[' '' = yes ']'
> >> + PS1='${debian_chroot:+($debian_chroot)}\u:\W\$ '
> >> + export GIT_TRACE_PACKET=1
> >> + GIT_TRACE_PACKET=1
> >> + export GIT_TRACE=1
> >> + GIT_TRACE=1
> >>>>>End of Lines from $HOME/.bashrc
> >> ## WHERE DOES The following line COME FROM????What Script spits out
> >> this line????
> >> + user1@Host2 git-upload-pack /srv/centralrepo
> >
> > Try set GIT_TRACE=1 at the clone line, I have a feeling that this line should be "ssh user@Host2..." but "ssh" is missing.
> >
> > $ export GIT_TRACE=1
> > $ git clone -v ssh://user1@Host2/srv/centralrepo
> > --
> > Duy
> >
> >
> > -----
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2016.0.7442 / Virus Database: 4537/11702 - Release Date: 02/26/16
> >
> >
>
>
>
> --
> Duy
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-29 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 23:03 Trouble Cloning Git remote repository Fred's Personal
2016-02-27 9:35 ` Duy Nguyen
2016-02-28 17:48 ` Fred's Personal
2016-02-29 1:20 ` Duy Nguyen
2016-02-29 9:34 ` John Keeping [this message]
2016-03-01 15:04 ` Fred's Personal
2016-03-01 15:28 ` 'John Keeping'
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=20160229093451.GC1766@serenity.lan \
--to=john@keeping.me.uk \
--cc=freddiewik@optonline.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).