From: "David D. Kilzer" <ddkilzer@kilzer.net>
To: git@vger.kernel.org
Cc: Eric Wong <normalperson@yhbt.net>,
"David D. Kilzer" <ddkilzer@kilzer.net>
Subject: Re: [BUG/TEST] git-svn: fetch fails with deleted tag
Date: Wed, 11 Aug 2010 22:18:39 -0700 (PDT) [thread overview]
Message-ID: <765385.99383.qm@web30004.mail.mud.yahoo.com> (raw)
In-Reply-To: <1281159415-60900-1-git-send-email-ddkilzer@kilzer.net>
On Fri, August 6, 2010 at 10:36:55 PM, David D. Kilzer wrote:
> The attached test fails when fetching the svn repo:
>
> Checksum mismatch: ChangeLog 065854....
> expected: ce771b....
> got: 9563fd....
>
> The issue seems to be that the tag was created, deleted and then
> recreated from the same source revision but at different paths.
I have a fix for this. I hope to send it out by Friday for further review.
This bug affects svn tags that are created, deleted and recreated with the
following criteria:
- Both tags have the same name (since the second one replaces the first one
after it's deleted).
- Both tags were created from the same revision in the repository.
- Each tag used a different repository path, e.g., one was from trunk while the
other was from a branch.
- [Optional] Both tags had a file with the same path name but different content.
If the optional fourth criteria is met, the checksum mismatch occurs and git-svn
fails during import.
However, if only the first three criteria are met, git-svn actually creates a
tag with the first (deleted) tag's content! The second tag's content is never
imported, leaving the user with a tag in git whose content doesn't match the
latest tag in svn.
Dave
next prev parent reply other threads:[~2010-08-12 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 5:36 [BUG/TEST] git-svn: fetch fails with deleted tag David D. Kilzer
2010-08-12 5:18 ` David D. Kilzer [this message]
2010-08-12 8:11 ` 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=765385.99383.qm@web30004.mail.mud.yahoo.com \
--to=ddkilzer@kilzer.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).