[MERGE] --no-backup option for bzr upgrade (#118653)

[Robert Collins]

On Tue, 2007-07-10 at 17:19 +0200, Lukáš Lalinský wrote:
> On St, 2007-07-11 at 01:01 +1000, Robert Collins wrote:
> > However --no-backup is really very dangerous; more dangerous than you
> > might predict.
> > 
> > Specifically any sort of link error will leave branches/repositories in
> > an unrecoverable state if no backup has been taken.
> 
> For this particular case, I don't think this is a big problem, because
> you can simple re-upload the code to launchpad. But I understand that in
> general is --no-backup a bad idea.
> 
> > Further to that some
> > upgrades will use the backup as the source for the upgraded data so we
> > may not be able to avoid it per se without changing where we make the
> > backup too... 
> 
> Hmm, it looks like some upgrade tests are missing because no backup
> doesn't break any of them. :)

Uhm, possibly I was wrong about current code using the backup. Looks
like it takes another backup inside the dir; anyhow - that is something
that obviously could be fixed.

The problem with unrecoverability is *much* more important and harder to
solve though.

Theres no way to tell that a use actually has a local copy - its
entirely possible for people to work solely with lightweight checkouts
against launchpad, and in this case there is no local copy to re-upload
in the event of failure.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070720/454fb30b/attachment.pgp