From: Tzafrir Cohen <tzafrir.cohen@xorcom.com>
To: git@vger.kernel.org
Subject: git-svn: Cannot lock the ref 'refs/remotes/tags/autotag_for_.'.
Date: Tue, 9 Feb 2010 23:39:29 +0200 [thread overview]
Message-ID: <20100209213929.GL3599@xorcom.com> (raw)
Hi
I'm using git-svn for watching over SVN repositories in
svn.asterisk.org . The largest one there is
http://svn.asterisk.org/svn/asterisk .
This worked fine up until recently. I was using Debian Stable with Git
1.5.6 .
Recently I upgraded my system to Debian Testing with Git 1.6 (I
currently have 1.6.6.1-1). Today I tried to update the repository (git
svn rebase --fetch-all) and got the following error:
fatal: Cannot lock the ref 'refs/remotes/tags/autotag_for_.'.
IIRC it followed an automatic garbage-collection in the repository.
I decided to re-clone the SVN repository (I was planning on doing that
for quite some time, with a proper AUTHORS file this time. But it's a
repo of some 200,000 revisions and takes a few days to clone)
I eventually got the same error.
The specific revision that triggered it:
http://svnview.digium.com/svn/asterisk?view=revision&revision=47394
Should git-svn mangle SVN tag names to be legal git ref names? Or just
panic before it makes the git repo invalid?
Is there a way for me to skip some tags? I can avoid that specific tag.
Please CC your replies to me as I don't actively follow this list.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir
next reply other threads:[~2010-02-09 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 21:39 Tzafrir Cohen [this message]
2010-02-10 17:07 ` git-svn: Cannot lock the ref 'refs/remotes/tags/autotag_for_.' Tzafrir Cohen
2010-02-11 8:36 ` Tay Ray Chuan
2010-02-12 14:41 ` Tzafrir Cohen
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=20100209213929.GL3599@xorcom.com \
--to=tzafrir.cohen@xorcom.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.