Re: Trouble Cloning Git remote repository

['John Keeping' <john@keeping.me.uk>]

On Tue, Mar 01, 2016 at 10:04:49AM -0500, Fred's Personal wrote:
> Thanks for the insight, it's been a while since I debugged a Windows call
> stack. Can you give me commands to view what gets passed to
> CreateProcessW().

Sorry, my Windows knowledge is several years old.  Maybe procmon[1] will
show them?

[1] https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx

> -----Original Message-----
> From: John Keeping [mailto:john@keeping.me.uk] 
> Sent: Monday, February 29, 2016 4:35 AM
> To: Duy Nguyen
> Cc: Fred's Personal; Git Mailing List
> Subject: Re: Trouble Cloning Git remote repository
> 
> 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
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7442 / Virus Database: 4537/11716 - Release Date: 02/28/16
> 
> 
> --
> 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