Creating a backup when upgrading should be optional

[Rune Philosof]

It might be that the user already has a backup (for instance from the previous crashed attempt to upgrade).
With large repositories it can take a long time to make a backup.
So make it optional!

[Martin Pool (mbp)]

We do use the other copy while upgrading, in at least some cases, but we could delete it when we're done.

[Rune Philosof (olberd)]

Do you change anything in the copy while upgrading?
In the case where the user already has a backup, it would be very nice with an option to point to an existing backup.

I am trying to debug bzr on a repository of 16GB (nfs mounted), so it takes a while for it to do the backup when I want to test if bzr can upgrade it.

[Martin Pool (mbp)]

On 10 March 2010 18:48, Olberd <email address hidden> wrote:
> Do you change anything in the copy while upgrading?

No, it's just a copy.

> In the case where the user already has a backup, it would be very nice with an option to point to an existing backup.

That would be a nice way to solve this bug. It's probably reasonably
easy to do if you want to try it.

> I am trying to debug bzr on a repository of 16GB (nfs mounted), so it
> takes a while for it to do the backup when I want to test if bzr can
> upgrade it.

I see.

--
Martin <http://launchpad.net/~mbp/>

[Martin Pool (mbp)]

Oh, actually there is a better workaround: create a new repository in the desired format, then branch into it. This will be approximately as fast as upgrading in place (except for tiny upgrades) and it will avoid making a copy.