bzr branch should be resumable if interrupted

Bug #116148 reported by John A Meinel
This bug affects 10 people
Affects Status Importance Assigned to Milestone

Bug Description

If you do "bzr branch http://upstream local" and cancel it half-way through, it should be possible to "cd local; bzr pull" to finish pulling.

At the moment, 'bzr branch' doesn't create a target branch until after the repository is copied. The current workaround is:

bzr branch http://upstream local
cd local
bzr init
bzr pull http://upstream

This has some small issues if the source is not the default format, etc. But it does let you re-use whatever data has been downloaded.

Alternatively, if you have a local shared repository, the data is stored there, so doing:

bzr init-repo --trees repo
cd repo
bzr branch http://upstream local
rm -rf local
bzr branch http://upstream local

Should only copy the extra bits that it needs.

As an aside, because of how things are copied, all of inventory.knit is downloaded again. It would be nice if it could download data from file knits in an order that in knew when inventory revisions had been finished. (download in revision order, rather than file-id order). But that has its own problems.

John A Meinel (jameinel)
Changed in bzr:
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
Revision history for this message
Matteo Settenvini (tchernobog) wrote :

Any news on this?

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 116148] Re: bzr branch should be resumable if interrupted

2009/1/12 Matteo Settenvini <email address hidden>:
> Any news on this?

In a future version of this code we'll commit the write group part way
through so that the data is still visible if the command is
interrupted. But, that's not done yet.

Martin <>

Revision history for this message
Martin Pool (mbp) wrote :

see also bug 125067

Jelmer Vernooij (jelmer)
Changed in brz:
status: New → Triaged
importance: Undecided → Medium
tags: added: performance resume
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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