summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar eigengrau <eigengrau@web>2015-05-21 08:20:23 +0000
committerGravatar admin <admin@branchable.com>2015-05-21 08:20:23 +0000
commitdffc0cf238ca687a08db5779696b398efcfb84a5 (patch)
tree93a10f087a0bb6b8b5171744f83334d901bc8fc7
parentc5ff8e0e97262749dc1975972bc7c017e19d8015 (diff)
-rw-r--r--doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn31
1 files changed, 31 insertions, 0 deletions
diff --git a/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn
new file mode 100644
index 000000000..436342696
--- /dev/null
+++ b/doc/bugs/Stale_keys_not_forgotten_upon_git-annex_forget.mdwn
@@ -0,0 +1,31 @@
+### Please describe the problem.
+At some point, I migrated all my WORM-backed objects to SHA1E. I then squashed my master branch to get rid of any WORM references and dropped unused objects. Recently, I noticed that the git-annex branch still has all tracking information on the old WORM keys. I tried running git-annex forget, but the old keys are not purged, even though no (local or remote) branch refers to them and no git-annex repository has the data for these keys anymore. Should such keys be purged by git-annex forget, too?
+
+### What steps will reproduce the problem?
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+git init /tmp/repo
+cd /tmp/repo
+git annex init
+echo hi > file
+git annex add --backend=WORM file
+git commit -m init
+git annex migrate
+git commit -m migrated
+git checkout --orphan tmp
+git commit -m squashed
+git branch -m master -f
+git annex unused
+git annex dropunused 1 --force
+git annex forget --drop-dead --force
+git ls-tree -r git-annex | grep WORM
+
+# End of transcript or log.
+"""]]
+
+### What version of git-annex are you using? On what operating system?
+git-annex 5.20150508
+Linux 4.0.4
+