[prev in list] [next in list] [prev in thread] [next in thread]
List: git
Subject: Re: Fwd: Error with git-svn pushing a rename
From: Benjamin Pabst <benjamin.pabst85 () gmail ! com>
Date: 2013-11-18 17:59:49
Message-ID: CAM-uYMiSE-XxA7DSWQSwzZ2vwB_MP5gnxuTzEJ7Vw9LRj2nwWA () mail ! gmail ! com
[Download RAW message or body]
Hi Andy,
sadly I get the same error with a downgraded svn:
$ git --version
git version 1.8.4.2
$ svn --version
svn, version 1.7.10 (r1485443)
compiled Nov 18 2013, 18:43:16
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.
- handles 'http' scheme
- handles 'https' scheme
$ git svn dcommit
Committing to https://xxxxx.xxx/xxxxx ...
R /some/file => /some/new/filename
perl: subversion/libsvn_subr/dirent_uri.c:2500: svn_fspath__is_child:
Assertion `svn_fspath__is_canonical(child_fspath)' failed.
error: git-svn died of signal 6
Any idea what I should do next to get this working? I also tried with
a "$ git svn rebase" first, which throws no error (just an "already
up-to-date")...
Thanks for your help!
Regards
Ben
2013/11/15 Andreas Stricker <astricker@futurelab.ch>:
> Hi Benjamin
>
>> thanks for your link. Can you give me the exact version you
>> downgraded svn to?
>
> svn, Version 1.7.10 (r1485443)
>
> I tried to reproduce the problem with git version 1.8.4.2 and
> Subversion version 1.8.4 (r1534716) with a fresh and pristine
> subversion repo and a git-svn clone of it: I didn't manage to
> reproduce the rename issue. Then I switched subversion back to
> 1.7.10, created both the repo and the git-svn clone, switched
> againt to 1.8.4.2 and then got an error. Unfortunately I didn't
> check if the subversion perlbindings were regenerated, so I'm
> not exactly sure. I'll repeat the test again, as soon I've find
> the time.
>
> It looks like a fresh git svn clone may fix the problem.
>
> Regards, Andy
--
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic