This commit is contained in:
parent
e8f60e7daa
commit
d3cc84db3b
1 changed files with 3 additions and 1 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue