Failure during remote upgrade
Barry Warsaw
barry at canonical.com
Wed Sep 30 15:10:29 BST 2009
On Sep 30, 2009, at 9:19 AM, Aaron Bentley wrote:
> Barry Warsaw wrote:
>> Is it safe to run the upgrade again?
>
> You'll need to rename backup.bzr to .bzr, but otherwise, yes.
I guess I need to do that through sftp, right?
Also, I wonder if Bazaar doesn't have this upgrade safeguard exactly
backwards. For example, the standard *nix update dance is something
like:
* open file.new
* read file
* write file.new
* close file
* close file.new
* mv file.new file (atomic rename)
This is more robust because if something fails, you still have the
original file unchanged.
However, Bazaar does it backwards such that if something fails, as it
did in my case, you're kind of hosed until you take action to unwedge
things. Maybe 'bzr upgrade' should be changed to do its upgrade in a
new location and only move them when they succeed?
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 832 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090930/2aaf8e4b/attachment.pgp
More information about the bazaar
mailing list