Bazaar Subversion Plugin

Checkout from svn fails with error=inconsistent delta and reason=repeated file_id

Bug #1011115 reported by Janos Gyerik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Triaged
High
Unassigned

Bug Description

1. See the attachment with the full output of the failing checkout.

2. Most of the commits in this repository were created by bzr commits, and all the revisions that print 'inconsistent details in skipped record' were created by bzr commits.

3. The bzr version on the server at the time of commits was 2.0. I now upgraded to 2.5 (both server and client) to see if that resolves the problem but it doesn't, the output is exactly the same as before.

4. The original bzr working directory that created the commits works fine, can commit new revisions, and if copied to another computer 'bzr up' works fine too. However new checkouts don't work.

5. The repository is private, but I don't mind giving it to a developer if it helps

6. The result is the same whether I checkout in Mac OS X or Linux

7. I have a workaround, but this is a serious problem

Revision history for this message
Janos Gyerik (janos-gyerik) wrote :
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is happening because of an issue in an older bzr-svn version which caused it to push invalid metadata into Subversion. The bug has since been fixed, but this metadata is confusing bzr-svn because it means there is an inconsistent view of various parts of the data.

Revision history for this message
Janos Gyerik (janos-gyerik) wrote :

In which bzr-svn version is the fix you mention? Currently I am using the latest stable version in Mac OS X, which is bzr-2.5 and bzr-svn-1.2.1. I re-pushed my local bzr repository to a brand new Subversion repository but no luck, I still cannot checkout from this new svn repository using bzr.

Jelmer Vernooij (jelmer)
affects: bzr → bzr-builtin-plugins
affects: bzr-builtin-plugins → bzr-svn
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Can you reproduce it using a public repository? It's hard to say much about a private repository without lots of time-consuming back and forth.

Revision history for this message
Janos Gyerik (janos-gyerik) wrote :

I can not make the repository public. But I zipped it up and sent it to your email address, with steps to reproduce the problem 100% of the time. Feel free to share it with others if it helps debugging the issue, but do not make it public. Thanks, and I hope this helps.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Thanks; I can reproduce this with the repository you specified.

Unfortunately I don't have time to further investigate this at the moment though.

Changed in bzr-svn:
status: New → Incomplete
status: Incomplete → Triaged
importance: Undecided → High
Revision history for this message
amicitas (mir-amicitas) wrote :

I have just run into the problem as well, and can no longer update any of my bzr checkouts of the svn repository other than the one that originally made the commits. I can also not create a new checkout of the svn repository.

The original commits were made using bzr 2.5.1 and bzr-svn 1.2.2.

Is there anyway that I can repair the svn reposition so I can get access to it in bzr again?

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.