A question about the error: svn_fspath__is_canonical

I found this mailing list thread discussing the problem I'm currently
experiencing: http://git.661346.n2.nabble.com/Fwd-Error-with-git-svn-pushing-a-rename-td7599382.html

Apparently a patch was submitted to fix this bug and I'm trying to
figure out what version of what I need to fix this bug.  The inability
to rename a class is a pretty limiting.

My environment is probably different from most.  I'm using cygwin.
This makes it very difficult to use different versions of
git/svn/git-svn, but I'm interested in learning git more so I'm
willing to try whatever it takes.

$ git version
git version 1.8.3.4

$ svn --version
svn, version 1.8.5 (r1542147)
   compiled Nov 25 2013, 10:45:07 on x86_64-unknown-cygwin

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
  - using serf 1.3.3
  - handles 'http' scheme
  - handles 'https' scheme

Thanks for the help

--
Thanks,
Dan

-- 
CONFIDENTIALITY NOTICE: The information contained in this electronic 
transmission may be confidential. If you are not an intended recipient, be 
aware that any disclosure, copying, distribution or use of the information 
contained in this transmission is prohibited and may be unlawful. If you 
have received this transmission in error, please notify us by email reply 
and then erase it from your computer system.

Hi Dan,

Dan Kaplan wrote:

My environment is probably different from most.  I'm using cygwin.
This makes it very difficult to use different versions of
git/svn/git-svn, but I'm interested in learning git more so I'm
willing to try whatever it takes.

$ git version
git version 1.8.3.4

$ svn --version
svn, version 1.8.5 (r1542147)
   compiled Nov 25 2013, 10:45:07 on x86_64-unknown-cygwin

You have three choices:

 A) upgrade git to latest "master"
 B) upgrade subversion to latest "trunk"
 C) downgrade subversion to a version before that bug was introduced

(A) is probably simplest.  E.g., something like the following should work:

  git clone https://kernel.googlesource.com/pub/scm/git/git.git
  cd git
  make -j8
  make test; # optional, to verify that the git you built works ok
  export PATH=$(pwd)/bin-wrappers:$PATH

Now the updated git is in your $PATH and you can use it.

See INSTALL in the git source tree for more details.

Hope that helps,
Jonathan

Because I'm on cygwin, that's a little intimidating to me.  I've never
compiled sources on cygwin.  Do you think it'll still work?

On Fri, Jan 10, 2014 at 11:16 AM, Jonathan Nieder [off-list ref] wrote:

Hi Dan,

Dan Kaplan wrote:

quoted

My environment is probably different from most.  I'm using cygwin.
This makes it very difficult to use different versions of
git/svn/git-svn, but I'm interested in learning git more so I'm
willing to try whatever it takes.

$ git version
git version 1.8.3.4

$ svn --version
svn, version 1.8.5 (r1542147)
   compiled Nov 25 2013, 10:45:07 on x86_64-unknown-cygwin

You have three choices:

 A) upgrade git to latest "master"
 B) upgrade subversion to latest "trunk"
 C) downgrade subversion to a version before that bug was introduced

(A) is probably simplest.  E.g., something like the following should work:

  git clone https://kernel.googlesource.com/pub/scm/git/git.git
  cd git
  make -j8
  make test; # optional, to verify that the git you built works ok
  export PATH=$(pwd)/bin-wrappers:$PATH

Now the updated git is in your $PATH and you can use it.

See INSTALL in the git source tree for more details.

Hope that helps,
Jonathan

-- 
Thanks,
Dan

-- 
CONFIDENTIALITY NOTICE: The information contained in this electronic 
transmission may be confidential. If you are not an intended recipient, be 
aware that any disclosure, copying, distribution or use of the information 
contained in this transmission is prohibited and may be unlawful. If you 
have received this transmission in error, please notify us by email reply 
and then erase it from your computer system.

Dan Kaplan wrote:

                             Do you think it'll still work?

Yes, that's why I suggested it. ;-)

You might need to install the gcc-core, libcurl-devel, openssl-devel,
and subversion-perl packages first.

Regards,
Jonathan

On 2014-01-10 20.28, Jonathan Nieder wrote:

Dan Kaplan wrote:

quoted

                             Do you think it'll still work?

Yes, that's why I suggested it. ;-)

You might need to install the gcc-core, libcurl-devel, openssl-devel,
and subversion-perl packages first.

Regards,
Jonathan

Out of my head:
You probably need to install even:
make, expat-devel (or similar)

I had to convert every file from windows line endings to unix line
endings with dos2unix (dos2unix was a separate install).  I did that
with this command: find . -type f | xargs dos2unix

I also had to install: libiconv, gettext, expat, gettext-devel, expat-devel

That got my make -j8 to run without error.

I then ran make test and it looked like most of the passed.  I added
it to my path and now my bug is fixed!  Thanks for the help guys.


On Fri, Jan 10, 2014 at 11:34 AM, Torsten Bögershausen [off-list ref] wrote:

On 2014-01-10 20.28, Jonathan Nieder wrote:

quoted

Dan Kaplan wrote:

quoted

                             Do you think it'll still work?

Yes, that's why I suggested it. ;-)

You might need to install the gcc-core, libcurl-devel, openssl-devel,
and subversion-perl packages first.

Regards,
Jonathan

Out of my head:
You probably need to install even:
make, expat-devel (or similar)

-- 
Thanks,
Dan

-- 
CONFIDENTIALITY NOTICE: The information contained in this electronic 
transmission may be confidential. If you are not an intended recipient, be 
aware that any disclosure, copying, distribution or use of the information 
contained in this transmission is prohibited and may be unlawful. If you 
have received this transmission in error, please notify us by email reply 
and then erase it from your computer system.