From: Eric Wong <normalperson@yhbt.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: latest update to git-svn blows up for me
Date: Mon, 4 Dec 2006 11:54:52 -0800 [thread overview]
Message-ID: <20061204195452.GB27342@soma> (raw)
In-Reply-To: <86zma3lahj.fsf@blue.stonehenge.com>
"Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> >>>>> "Eric" == Eric Wong <normalperson@yhbt.net> writes:
>
> Eric> "Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> >> >>>>> "Eric" == Eric Wong <normalperson@yhbt.net> writes:
> >>
> Eric> "Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> >> >>
> >> >> Does this ring a bell?
> >>
> Eric> Nope.
> >>
> Eric> This is on r15941 of https://svn.perl.org/parrot/trunk ? I can't seem
> Eric> to reproduce this with git svn fetch -r15940:15941
> >>
> >> No, and that worked for me as well. Apparently, I might have corrupted my
> >> metadata because I updated git-svn while I was using it. Is there any way to
> >> reset the metadata without having to re-fetch 15000 revisions?
>
> Eric> rm .git/refs/remotes/$GIT_SVN_ID .git/svn/$GIT_SVN_ID/.rev_db
> Eric> git svn -i $GIT_SVN_ID rebuild
>
> That's not working:
>
> localhost.local:..RROR/parrot-GITSVN % git-svn -i git-svn rebuild
> fatal: 'origin': unable to chdir or not a git archive
> fatal: unexpected EOF
> Failed to find remote refs
> 256 at /opt/git/bin/git-svn line 2151
> main::safe_qx('git-ls-remote', 'origin', 'refs/remotes/git-svn') called at /opt/git/bin/git-svn line 3404
> main::copy_remote_ref() called at /opt/git/bin/git-svn line 226
> main::rebuild() called at /opt/git/bin/git-svn line 187
Can you try:
git update-ref refs/remotes/git-svn \
<last commit successfully imported from git-svn>
and running rebuild again?
--
next prev parent reply other threads:[~2006-12-04 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 4:00 latest update to git-svn blows up for me Randal L. Schwartz
2006-12-04 7:00 ` Eric Wong
2006-12-04 11:41 ` Randal L. Schwartz
2006-12-04 18:12 ` Eric Wong
2006-12-04 19:36 ` Randal L. Schwartz
2006-12-04 19:54 ` Eric Wong [this message]
2006-12-04 20:04 ` Randal L. Schwartz
2006-12-04 20:08 ` Eric Wong
2006-12-04 20:10 ` Randal L. Schwartz
2006-12-04 20:51 ` Eric Wong
2006-12-05 4:08 ` Eric Wong
2006-12-05 4:19 ` Randal L. Schwartz
2006-12-05 4:33 ` Randal L. Schwartz
2006-12-05 9:13 ` Eric Wong
2006-12-05 16:47 ` Linus Torvalds
2006-12-08 9:55 ` [PATCH] git-svn: extra error check to ensure we open a file correctly Eric Wong
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=20061204195452.GB27342@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).