git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Morgan Christiansson <git@mog.se>
Cc: git@vger.kernel.org
Subject: Re: git-svn: File was not found in commit
Date: Sun, 11 Jan 2009 22:55:26 +0100	[thread overview]
Message-ID: <20090111215526.GA15533@atjola.homenet> (raw)
In-Reply-To: <49678705.4040506@mog.se>

On 2009.01.09 18:19:01 +0100, Morgan Christiansson wrote:
> Hi, i'm trying to "git svn fetch" my repository from a local file:///
> repo and i'm running into this problem:
>
> $ git svn init -t tags -b branches -T trunk file:///path/to/svn/repo
> $ git svn fetch
> branches/rails/rails/vendor/plugins/acts_as_xapian/.git/refs/heads/master
> was not found in commit a643e882c557593f36bb9fd0966490010b9dba61 (r10576)
>
>
> I found another report that seems to describe the same error:
> http://marc.info/?l=git&m=121537767308135&w=2
> Investigating the the history it's committed in r10577 and it's looking
> for it in r10576, so it seems to be off by one revision number. Exactly
> like the other report.
> I've tried the latest git version of git-svn.perl and the problem is not
> fixed there.
>
>
> $ svn log file:///path/to/repo -r10576:10577 -v
> ------------------------------------------------------------------------
> r10576 | morgan | 2008-11-28 14:35:53 +0000 (Fri, 28 Nov 2008) | 3 lines
> Changed paths:
>   A /branches/rails/rails/app/controllers/browse_sheetmusic_controller.rb
>   M /branches/rails/rails/app/controllers/scores_controller.rb
>   M /branches/rails/rails/app/models/composer.rb
>   M /branches/rails/rails/app/models/score.rb
>   M /branches/rails/rails/config/routes.rb
>
> Commit message.
>
> ------------------------------------------------------------------------
> r10577 | morgan | 2008-11-28 18:31:00 +0000 (Fri, 28 Nov 2008) | 3 lines
> Changed paths:
>   A /branches/rails/rails/vendor/plugins/acts_as_xapian/.git/FETCH_HEAD
>   M /branches/rails/rails/vendor/plugins/acts_as_xapian/.git/config
>   M /branches/rails/rails/vendor/plugins/acts_as_xapian/.git/index
>   M /branches/rails/rails/vendor/plugins/acts_as_xapian/.git/logs/HEAD
>   M
 
> /branches/rails/rails/vendor/plugins/acts_as_xapian/.git/logs/refs/heads/master 
> 
>
> # <-- THIS FILE

Unless I totally misread that line, SVN reports that the file was
_modified_, not added. For the file to be modified, it seems reasonable
to expect that it existed in the previous commit.

Is there anything "special" about how that file came into existence in
that branch? Without further knowledge, that looks like a svn bug, but
hey, it's svn, it might do funny stuff on purpose ;-)

Maybe you could provide a small test case/repo?

Björn

  parent reply	other threads:[~2009-01-11 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 17:19 git-svn: File was not found in commit Morgan Christiansson
2009-01-11 18:36 ` Morgan Christiansson
2009-01-11 21:55 ` Björn Steinbrink [this message]
2009-01-12  0:04   ` Morgan Christiansson
2009-01-12  2:32     ` Eric Wong
2009-01-12  5:14       ` Eric Wong
2009-01-12 13:45         ` Morgan Christiansson
2009-01-19  2:41           ` 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=20090111215526.GA15533@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=git@mog.se \
    --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 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).