Branch.revision_history RPC fails on a stacked branch

Bug #380314 reported by Andrew Bennetts on 2009-05-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Andrew Bennetts

Bug Description

The Branch.revision_history RPC fails on a stacked branch because the "branch.revision_history()" call on the server fails (because not all the history is accessible). This affects e.g. "bzr pull --revision 123"

We should add a new verb that can send an incomplete history without failing, and then make the client ask the fallback(s) for the rest of the history.

Related branches

Andrew Bennetts (spiv) on 2009-05-25
Changed in bzr:
importance: Undecided → High
milestone: none → 1.16
status: New → Confirmed
Jonathan Lange (jml) wrote :

On IRC, Andrew said he was working on this. Assigning to him to make release tracking easier.

Changed in bzr:
assignee: nobody → Andrew Bennetts (spiv)
status: Confirmed → Triaged
Jonathan Lange (jml) on 2009-06-10
Changed in bzr:
status: Triaged → In Progress
Andrew Bennetts (spiv) wrote :

The fix for this has landed in r4432.

Changed in bzr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers