From: Joey Hess Date: Mon, 9 Mar 2020 17:45:06 +0000 (-0400) Subject: bug report X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~104^2~18 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=e57f64ce8928bfd63de067d724d2bbc7670cbb5d;p=git-annex.git bug report --- diff --git a/doc/bugs/v7_upgrade_of_local_clone_bug.mdwn b/doc/bugs/v7_upgrade_of_local_clone_bug.mdwn new file mode 100644 index 0000000000..3c96c32b70 --- /dev/null +++ b/doc/bugs/v7_upgrade_of_local_clone_bug.mdwn @@ -0,0 +1,20 @@ +When a local clone was at v7 and gets upgraded to v8 by a command run in +a repo that has it as a remote, this is displayed: + +"fatal: ../path/to/clone is outside repository" + +This happens because git ls-files is run to list the files of the clone. +But, it has some strange behavior when relative paths are used. Result is +it always fails. This also causes the keys database of the clone to not get +repopulated after being deleted for the upgrade. That's not a fatal problem +because git-annex is always prepared for the keys database being out of +date, but it could result in considerably more work being done later. + +I also found some v1 upgrade code that does the same thing, and presumably +also has the problem, although there are probably no v1 repos left. +This seems like it could be a larger problem that only upgrades, but +luckily upgrades seem like the only time that git-annex, running in one +repo, needs to do anything involving listing the files in the working tree +of a remote. + +--[[Joey]