c6e693b25d
For reasons explained in the bug report. Implemented using a persistent migration, which works fine. It may add a little startup overhead when a remote is enabled that uses this, but probably un-noticable. On the next major version, it would be fine to delete this database, and regenerate it from the git-annex branch information. Then this change could be reverted. Did nothing about adding back the data that got dropped from the db due to the bug. Only the borg special remote was probably affected, and it's not been released yet. rm -rf .git/annex/cidsdb does work. |
||
|---|---|---|
| .. | ||
| Keys | ||
| Benchmark.hs | ||
| ContentIdentifier.hs | ||
| Export.hs | ||
| Fsck.hs | ||
| Handle.hs | ||
| Init.hs | ||
| Keys.hs | ||
| Queue.hs | ||
| Types.hs | ||