bzr 2.2.0b1 will create backup.bzr.~1~

[Martin Pool]

The fix for bug 335033 is in bzr 2.2.0b1 and will cause bzr to create backup.bzr.~1~ etc directories on upgrade, rather than backup.bzr. Launchpad might need changes to cope.

[Paul Hummer (rockstar)]

So if backup.bzr exists, backup.bzr.~1~ will be created, and if backup.bzr.~1~ exists as well, it will create backup.bzr.~2~ ? If so, this would be a really good bug to fix, since we currently remove backup.bzr if it exists, and that's always scary to do.

[Martin Pool (mbp)]

On 19 February 2010 08:39, Paul Hummer <email address hidden> wrote:
> So if backup.bzr exists, backup.bzr.~1~ will be created, and if
> backup.bzr.~1~ exists as well, it will create backup.bzr.~2~ ?

Yes.

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

[Tim Penhey (thumper)]

On Fri, 19 Feb 2010 10:46:43 Martin Pool wrote:
> On 19 February 2010 08:39, Paul Hummer <email address hidden> wrote:
> > So if backup.bzr exists, backup.bzr.~1~ will be created, and if
> > backup.bzr.~1~ exists as well, it will create backup.bzr.~2~ ?
>
> Yes.

  status triaged
  importance high
  tag codehosting-ssh

The VFS needs to be changed to allow these types of files, as well as the
upgrade job.

[Paul Hummer (rockstar)]

Talking with abentley, we'll need to allow these new directories to exist on the VFS, because right now, they aren't allowed. We only allow .bzr, backup.bzr and .bzr-backup

[Jelmer Vernooij (jelmer)]

This was fixed by Rob in 10691.1.1.