Upgrade can leave a broken repository (with backup)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
I just had the following sequence:
Using saved location: http://
bzr: ERROR: Tags not supported by BzrBranch5(
"Hmm, isn't --dirstate-tags default now?"
jw2328@
starting upgrade of file://
making backup of tree history
file://
if conversion fails, you can move this directory back to .bzr
if it succeeds, you can remove this directory if you wish
starting repository conversion
bzr: ERROR: Cannot convert to format <RepositoryForm
"Ok, that's not good, let's try --dirstate-tags explictly"
jw2328@
bzr: ERROR: No repository present: "file:/
jw2328@
total 48
drwxr-xr-x 3 jw2328 jw2328 4096 2007-09-27 21:58 branch
-rw-r--r-- 1 jw2328 jw2328 35 2007-07-12 18:12 branch-format
drwxr-xr-x 2 jw2328 jw2328 4096 2007-07-12 18:12 branch-lock
drwxr-xr-x 3 jw2328 jw2328 4096 2007-07-12 18:31 checkout
-rw-r--r-- 1 jw2328 jw2328 82 2007-07-12 18:12 README
drwxr-xr-x 5 jw2328 jw2328 4096 2007-07-12 18:12 repository.backup
"Ah, repository backed up, but not there"
Now the upgrade failed and no commands work. Surely a failure to upgrade due to the
type should notice before removing the repository.
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: check-for-breezy |
status triaged
importance low
The code path upgrade uses in this case is:
'backup'
'create a new repository in the requested format'
'perform a fetch'
The problem is that the api that is failing currently has to be called
to fail.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://