From c21c0cd885ab0f88bcb65bd58565994e47932082 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 27 Aug 2019 15:45:43 -0400 Subject: [PATCH] update with WSL findings --- doc/todo/v7_path_toward_default.mdwn | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/doc/todo/v7_path_toward_default.mdwn b/doc/todo/v7_path_toward_default.mdwn index 8f412b295a..41b3993bdd 100644 --- a/doc/todo/v7_path_toward_default.mdwn +++ b/doc/todo/v7_path_toward_default.mdwn @@ -24,6 +24,12 @@ Limited mostly to windows, also some FAT media. This seems difficult to avoid though, see discussion in +On Windows Subsystem for Linux, adusted branches don't work due to +some problem with sqlite, so upgrading a direct mode repo there +would be a problem. + +But, regular v5 and v7 repos do work in WSL. + done ## step 4: default for all new repositories @@ -42,9 +48,9 @@ course change behavior though. The only significant difference is that Annex.Content in v7 reads and writes to the keys database. So any problem with the database -code would prevent using git-annex. On Windows, sqlite does not currently -work in WSL. http://git-annex.branchable.com/bugs/WSL_adjusted_braches__58___smudge_fails_with_sqlite_thread_crashed_-_locking_protocol/ -So this would make git-annex maybe not work on WSL until that's fixed. +code could prevent using git-annex. WSL has such a problem currently, +but it doesn't seem to affect using v7 repos, only adjusted branches. + A concern is that a v5 repository may be used by multiple machines, some not supporting v7 and some that do. If one upgrades to v7