All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Schaible" <joerg.schaible@swisspost.com>
To: git@vger.kernel.org
Subject: git svn clone fails
Date: Wed, 29 Jul 2015 12:12:01 +0200	[thread overview]
Message-ID: <mpa8th$m80$1@ger.gmane.org> (raw)

Hello guys,

we have to turn some projects managed by Subversion into a GIT-based 
solution. However the conversion unfortunately fails with an error:

============== %< ==============
[...]
Found branch parent: (refs/remotes/origin/tags/v_2.1.1) 
450fa2c84a8fc087a2a66e5fb3d6d22096671f81
Following parent with do_switch
        M       changes.xml
        M       pom.xml
couldn't truncate file at /usr/lib64/perl5/vendor_perl/5.20.2/Git.pm line 
1325.
$ git --version
git version 2.5.0
============== %< ==============

Apart from the line number, the same error occurs also with GIT version 
2.4.6 and 2.3.6 (latest stable version in Gentoo).

The command to create the GIT repository was:
============== %< ==============
$ git svn clone http://websvn/svn/essvn/standard/java-commons/lang -s --no-
metadata --preserve-empty-dirs -A ~/tmp/authors.txt commons-lang
============== %< ==============

Note, that the command succeeds even for 2.4.6 if we drop the --preserve-
empty-dirs option - at the cost of some empty directories which are used to 
trigger profiles for Maven; i.e. without those we cannot reproduce released 
versions.

Cheers,
Jörg

             reply	other threads:[~2015-07-29 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 10:12 Jörg Schaible [this message]
2015-08-04  8:20 ` git svn clone fails Jörg Schaible
2015-08-14  7:51   ` Jörg Schaible
2015-08-14  8:32     ` Torsten Bögershausen
2015-08-14 10:38       ` Jörg Schaible
2015-08-14 11:54         ` Torsten Bögershausen
2015-08-14 13:47           ` Jörg Schaible
2015-09-02  2:27     ` Eric Wong
2015-09-03 12:19       ` Jörg Schaible

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='mpa8th$m80$1@ger.gmane.org' \
    --to=joerg.schaible@swisspost.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.