Failure during remote upgrade

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barry Warsaw wrote:
> On Sep 30, 2009, at 10:10 AM, Barry Warsaw wrote:
> 
>> 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?
> 
> Nope, this failed.

It failed because you're not renaming backup.bzr to .bzr.

Codehosting only permits a few top-level filenames: ".bzr", "backup.bzr"
and ".bzr.backup" (obsolete).  This is because we want to host Bazaar
branches and nothing else.

By renaming backup.bzr to backup.bzr.failed, you are trying to create a
forbidden filename.  The same is true when you try to rename .bzr to
.bzr.failed.

> LOSA time?

No, not needed.

> However, it's odd that there's a .bzr directory and a backup.bzr
> directory.  I don't know how to crawl out of this hole. :(

There is a backup directory in case something went wrong with the
conversion.  It is retained even after the conversion is complete, as a
paranoid measure,  in case the conversion was somehow faulty.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrDa8wACgkQ0F+nu1YWqI2JQgCfYbN4/FMRcMo3m4Jsp/qGFiwc
x5UAoIfKD/1/4NG2tpZB0d4FYOpKbSMY
=n+Hp
-----END PGP SIGNATURE-----