From d3cc84db3b2efe9e1b57ae3e8f7bad4902408c6a Mon Sep 17 00:00:00 2001 From: "git-annex@82b5fddc759dffdf749b19add6f0be2a0c78b62c" Date: Wed, 7 Aug 2024 12:05:53 +0000 Subject: [PATCH] --- doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 index e5f5db98f5..5da767cea8 100644 --- a/doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn +++ b/doc/bugs/migrate_does_not_migrate_from_SHA256E_to_SHA256.mdwn @@ -1,5 +1,7 @@ ### 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. +In my repository I have a mixture of SHA256 and SHA256E backed files 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), some files pointing to SHA256E files still point to SHA256E instead of, as expected, SHA256. + +Note: The migration actually migrated MOST of the files, but some remain. I don't see anything special about these files. 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.