Proper URI for "svn clone" on a network share (Win32)

Proper URI for "svn clone" on a network share (Win32)

[Tim Chase]

I've been sparring with the proper syntax and hope someone can give
me the magic I'm missing.  I want to do something of the form

  c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"

but get various failures.  My best-effort (above) gets me as far as
actually starting some sort of clone but it dies with

"""
Permission denied: Can't open '/tmp/report.tmp': Permission denied 
at /usr/lib/perl5/site_perl/Git/SVN.pm line 1210
"""

If it makes any difference, this is within a cmd.exe shell (with $PATH
set appropriately so git is being found).

Am I missing something in the URL syntax to get it to clone my svn
repo with less drama?

-tkc

PS: I don't really care much about pushing back to svn, existing
svn branches or tags, or username mapping.  If needed, I can apply
patches out of git which is far less painful than switching/merging
branches in svn.  So I can be a little rough-shod with cloning the
svn repo.

PPS: in case it matters:
C:\work\utils\temp\ios>git version
git version 1.8.3.msysgit.0



.

Re: Proper URI for "svn clone" on a network share (Win32)

[Tim Chase]

On 2013-08-14 12:49, Tim Chase wrote:
> If it makes any difference, this is within a cmd.exe shell (with
> $PATH set appropriately so git is being found).

Just a follow-up, I tried it within the "bash"ish shell included in
the git install and got the same error regarding "/tmp/report.tmp".

-tkc

Re: Proper URI for "svn clone" on a network share (Win32)

[John Keeping]

On Wed, Aug 14, 2013 at 06:26:57PM -0500, Tim Chase wrote:
> On 2013-08-14 12:49, Tim Chase wrote:
> > If it makes any difference, this is within a cmd.exe shell (with
> > $PATH set appropriately so git is being found).
> 
> Just a follow-up, I tried it within the "bash"ish shell included in
> the git install and got the same error regarding "/tmp/report.tmp".

It seems that report.tmp is something that SVN creates and for some
reason the svn on your system is trying to create it in a Unix style
temporary directory.

What happens if you export TMPDIR=C:/Windows/Temp before running
git-svn?

Re: Proper URI for "svn clone" on a network share (Win32)

[Tim Chase]

On 2013-08-15 09:00, John Keeping wrote:
> On Wed, Aug 14, 2013 at 06:26:57PM -0500, Tim Chase wrote:
> > On 2013-08-14 12:49, Tim Chase wrote:
> > > If it makes any difference, this is within a cmd.exe shell (with
> > > $PATH set appropriately so git is being found).
> > 
> > Just a follow-up, I tried it within the "bash"ish shell included
> > in the git install and got the same error regarding
> > "/tmp/report.tmp".
> 
> It seems that report.tmp is something that SVN creates and for some
> reason the svn on your system is trying to create it in a Unix style
> temporary directory.
> 
> What happens if you export TMPDIR=C:/Windows/Temp before running
> git-svn?

Still getting the same results.  I tried:

1) cmd.exe with my local temp dir:
 c:\temp> TEMPDIR=%TEMP%
 c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"

2) cmd.exe with the windows temp dir as you specify:
 c:\temp> TEMPDIR=c:\windows\temp
 c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"

3) git's bash.exe with inline variable definition:
 $ TEMPDIR=c:/Windows/Temp git svn clone "file:///x:/path/to/repo/trunk/utils/project1"

4) git's bash.exe with exported variable:
 $ export TEMPDIR=c:/Windows/Temp
 $ git svn clone "file:///x:/path/to/repo/trunk/utils/project1"

All of them died with the complaint about "/tmp/report.tmp"

Thanks for the suggestion though.  At least we've determined one
thing that *isn't* the issue ;-)

-tkc

Re: Proper URI for "svn clone" on a network share (Win32)

[John Keeping]

On Thu, Aug 15, 2013 at 06:12:29AM -0500, Tim Chase wrote:
> On 2013-08-15 09:00, John Keeping wrote:
> > On Wed, Aug 14, 2013 at 06:26:57PM -0500, Tim Chase wrote:
> > > On 2013-08-14 12:49, Tim Chase wrote:
> > > > If it makes any difference, this is within a cmd.exe shell (with
> > > > $PATH set appropriately so git is being found).
> > > 
> > > Just a follow-up, I tried it within the "bash"ish shell included
> > > in the git install and got the same error regarding
> > > "/tmp/report.tmp".
> > 
> > It seems that report.tmp is something that SVN creates and for some
> > reason the svn on your system is trying to create it in a Unix style
> > temporary directory.
> > 
> > What happens if you export TMPDIR=C:/Windows/Temp before running
> > git-svn?
> 
> Still getting the same results.  I tried:
> 
> 1) cmd.exe with my local temp dir:
>  c:\temp> TEMPDIR=%TEMP%

This should be TMPDIR - note the missing 'E'!

You may also need to "export TMPDIR" but I don't know how cmd.exe
decides what environment variables to export to subprocesses.

>  c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
> 
> 2) cmd.exe with the windows temp dir as you specify:
>  c:\temp> TEMPDIR=c:\windows\temp
>  c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
> 
> 3) git's bash.exe with inline variable definition:
>  $ TEMPDIR=c:/Windows/Temp git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
> 
> 4) git's bash.exe with exported variable:
>  $ export TEMPDIR=c:/Windows/Temp
>  $ git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
> 
> All of them died with the complaint about "/tmp/report.tmp"
> 
> Thanks for the suggestion though.  At least we've determined one
> thing that *isn't* the issue ;-)

Re: Proper URI for "svn clone" on a network share (Win32)

[Tim Chase]

On 2013-08-15 12:35, John Keeping wrote:
>>>> Just a follow-up, I tried it within the "bash"ish shell
>>>> included in the git install and got the same error regarding
>>>> "/tmp/report.tmp".
>>> 
>>> It seems that report.tmp is something that SVN creates and for
>>> some reason the svn on your system is trying to create it in a
>>> Unix style temporary directory.
>>> 
>>> What happens if you export TMPDIR=C:/Windows/Temp before running
>>> git-svn?
>> 
>> Still getting the same results.
> 
> This should be TMPDIR - note the missing 'E'!

I wish I could blame it on my doofus mistype, but I tried the same 4
operations as my previous email, using "TMPDIR" this time instead of
"TEMPDIR" but got the same errors regarding "/tmp/report.tmp".

> You may also need to "export TMPDIR" but I don't know how cmd.exe
> decides what environment variables to export to subprocesses.

>From my understanding/experimentation, cmd.exe acts as if all
environment variables are exported all the time (i.e., there is no
such thing as a "local" non-exported environment variable).

Any further ideas to try?

Thanks,

-tkc

Re: Proper URI for "svn clone" on a network share (Win32)

[Tim Chase]

On 2013-08-14 12:49, Tim Chase wrote:
>   c:\temp> git svn clone "file:///x:/path/to/repo/trunk/utils/project1"
> 
> but get various failures.  My best-effort (above) gets me as far as
> actually starting some sort of clone but it dies with
> 
> """
> Permission denied: Can't open '/tmp/report.tmp': Permission denied 
> at /usr/lib/perl5/site_perl/Git/SVN.pm line 1210
> """
> 
> PS: I don't really care much about pushing back to svn, existing
> svn branches or tags, or username mapping.  If needed, I can apply
> patches out of git which is far less painful than switching/merging
> branches in svn.  So I can be a little rough-shod with cloning the
> svn repo.
> 
> PPS: in case it matters:
> C:\work\utils\temp\ios>git version
> git version 1.8.3.msysgit.0

Just tickling this thread.  I tried John Keeping's suggestions on
setting TMPDIR to some known location, but I continue getting the same
error about "Can't open '/tmp/report.tmp': Permission denied..." both
in cmd.exe and within the bash.exe that comes with msysgit.

In additional peculiarity from my testing, if I point a true Linux
shell at the same network-mounted drive, it seems to work just fine:

  tim@host:/tmp$ git svn clone file:///mnt/svnroot/trunk/utils/project1
  tim@host:/tmp$ git --version
  git version 1.5.6.5

(yeah, that's a REALLY ancient version of git on an old Debian Lenny
box, but if *that* works, 1.8.x shouldn't have ANY trouble with it)

Any further ideas?

-tkc