aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-28 09:27:28 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-28 09:27:28 -0400
commit016eea028086f2e8c1733ac77612f4397297d1a3 (patch)
tree03c8c47d176524ed576c09ff8635b0206c8bdf8e /doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
parent9d86d02b3db23f0b8848f4a9a044befa58e1ecbb (diff)
Bugfix: Keys could be received into v1 annexes from v2 annexes, via v1 git-annex-shell. This results in some oddly named keys in the v1 annex. Recognise and fix those keys when upgrading, instead of crashing.
Diffstat (limited to 'doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn')
-rw-r--r--doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
index 64c18f202..1eebd9ecd 100644
--- a/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
+++ b/doc/bugs/backend_version_upgrade_leaves_repo_unusable.mdwn
@@ -56,3 +56,6 @@ Running the copy job again, I am still getting the same error as above (as expec
>>> you shouldn't delete anything. I'll simply make the v2 upgrade
>>> detect and work around this bug.
>>> --[[Joey]]
+
+>>>> This should be fixed in current git. The scambled keys will be
+>>>> fixed up on upgrade. Thanks for your patience! [[done]] --[[Joey]]