Ubuntu

git-svn creates wrong tag when latter contains spaces

Reported by Daniel D. on 2011-05-23
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
git (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: git

Importing https://svn.java.net/svn/jna~svn/trunk. There's a tag called "CVS HEAD" with a space. This causes git-svn to create .git/refs/remotes/tags/CVS%20HEAD, which is url-encoded. If git-svn dies, subsequent restarts fail. Workaround is to rename CVS HEAD, replace %20 by a space.

There're also warnings importing this repo, and a lot of git-svn died with signal 13. But those are separate problems.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: git-svn 1:1.7.4.1-3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Mon May 23 07:28:21 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: git
UpgradeStatus: Upgraded to natty on 2011-04-29 (24 days ago)

Daniel D. (dblock-dblock) wrote :
Daniel D. (dblock-dblock) wrote :

Command used is git svn --authors-file=authors clone -s https://svn.java.net/svn/jna~svn.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in git (Ubuntu):
status: New → Confirmed
kenorb (kenorb) wrote :

See:
http://stackoverflow.com/questions/11365317/git-svn-clone-fails-fatal-not-a-valid-object-name/11559472#11559472

I've the same problem:
$ git svn fetch
Found possible branch point: https://xxx/svn/xxx/branches/11-07 D t-m => https://xxx/svn/xxx/branches/11-09 S t-m, 4332
fatal: Not a valid object name refs/remotes/1-11 M R 2.6
cat-file commit refs/remotes/1-11 M R 2.6: command returned error: 128

Trying to create the tag manually, but it's not allowed.
$ git tag "11-07 D t-m" remotes/11-07%20D
fatal: '11-07 D t-m' is not a valid tag name.

kenorb (kenorb) wrote :

This is fixed in Git 1.8.0
https://github.com/git/git

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers