Bazaar Subversion Plugin

missing chk node(s) for id_to_entry maps for bzr-svn 1.1.0

Bug #887880 reported by Philip Peitsch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Expired
Undecided
Unassigned

Bug Description

This is a re-occurrence of bug #485601 in bzr-svn 1.1.0, which *should* have had the fix in it.

I've just encountered this between a system running bzr 2.4.1 and bzr 2.5.1, running bzr-svn 1.1.0 and 1.1.1dev.

The workflow *seems* to be as follows:

1.
user1 => bound to svn trunk
user2 => bound to svn trunk

2.
user1 commits a change to svn trunk
user2 updates their copy of svn trunk

3.
at a later time, user1 tries to branch directly from another of user2's feature branches made after the checkins occurred and experiences this error.

The exact working setup we have here is:

- Bazaar Server with a Shared Repository contains the master branch from SVN
- Individual devs create a local shared repo on their machines, and branch from the master branch
- Individual devs then bind their master branch directly to the SVN source branch in order to commit things to trunk
- Individual dev checkouts are bound to feature branches created on the Bazaar Server (in order to allow network backups)

The dev experienced the crash just after checking in to trunk. They had then just created a new feature branch, and the crash occured during the bzr switch command in their checkout to the new feature branch on the Bazaar Server

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

Sorry to see you're hitting this still.

Are both user branches created with bzr-svn 1.1.0 or 1.1.1 ? Can their repositories perhaps contain revisions created with older versions of bzr-svn?

This bug is caused by inconsistent data being pushed into svn by bzr-svn. A clone that was made by an older version of bzr-svn could
still be problematic.

Revision history for this message
Philip Peitsch (philip-peitsch) wrote :

Sorry... I didn't add as much info as I probably should have :)

In this case, the Bazaar Server is running 1.1.1dev, and is the only one on this version. The individual devs are running 2.4.1 on Windows boxes.

There should be no clones from previous versions. Prior to performing this upgrade, I got all devs to delete their local bazaar installs and branches (including the svn-cache folder), and then purged all the bzr: revprops out of the svn server. Have I missed anything you can think of?

Thanks for the patient work on this. I sympathize with how annoying recurring bugs can be!

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

Which version of bzr-svn are the individual developers running on their Windows machines?

Revision history for this message
Philip Peitsch (philip-peitsch) wrote : Re: [Bug 887880] Re: missing chk node(s) for id_to_entry maps for bzr-svn 1.1.0

1.1.0 was on all the Windows machines

On 13 November 2011 12:34, Jelmer Vernooij <email address hidden>wrote:

> Which version of bzr-svn are the individual developers running on their
> Windows machines?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/887880
>
> Title:
> missing chk node(s) for id_to_entry maps for bzr-svn 1.1.0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bzr-svn/+bug/887880/+subscriptions
>

--
Philip Peitsch
Mob: 0439 810 260

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

Could you run "bzr check" in the various branches?

1.1.1 has more fixes related to inconsistent file revisions, and was the first release to pass the full bzr per-repository testsuite. It might be worth to give that a try.

Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Bazaar Subversion Plugin because there has been no activity for 60 days.]

Changed in bzr-svn:
status: Incomplete → Expired
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.