From: git-annex@82b5fddc759dffdf749b19add6f0be2a0c78b62c <git-annex@web>
Date: Wed, 7 Aug 2024 12:04:42 +0000 (+0000)
Subject: (no commit message)
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~21^2~167
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=e8f60e7daa366322f3ee6c7ebf80b7ae7c2907b5;p=git-annex.git

---

diff --git a/doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn b/doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn
new file mode 100644
index 0000000000..e5f5db98f5
--- /dev/null
+++ b/doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn
@@ -0,0 +1,20 @@
+### Please describe the problem.
+In my repository I have a mixture of SHA256 and SHA256E backends due to old files and manually configuring a subset of the remotes to SHA256. After configuring SHA256 as the (only) backend, when I run git annex migrate (with or without giving a specific path, or specifying the target SHA256 backend), the files pointing to SHA256E files still point to SHA256E instead of, as expected, SHA256.
+
+Note: The issue is NOT that, after migration, the SHA256E files remain as "duplicates". This is annoying, but I'm aware of this and can mitigate the issue via dropunused.
+
+
+### What steps will reproduce the problem?
+Have SHA256E. Configure SHA256 as backend. Run migrate.
+
+
+### What version of git-annex are you using? On what operating system?
+10.20230126 (Debian Stable)
+
+
+### Please provide any additional information below.
+n/a
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+I love it! :)
+