From: Joey Hess Date: Mon, 12 Jul 2021 14:24:42 +0000 (-0400) Subject: update X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~2^2^2~69^2~111 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=0ea263a03615b5f08f7d76006827c710bf3097fc;p=git-annex.git update --- diff --git a/doc/bugs/regression__58___index.lck_in_shared-group_is_not_g+w/comment_3_621beade26a1dbbdea000ca43d93a325._comment b/doc/bugs/regression__58___index.lck_in_shared-group_is_not_g+w/comment_3_621beade26a1dbbdea000ca43d93a325._comment index ab42972f9f..e5ab4703aa 100644 --- a/doc/bugs/regression__58___index.lck_in_shared-group_is_not_g+w/comment_3_621beade26a1dbbdea000ca43d93a325._comment +++ b/doc/bugs/regression__58___index.lck_in_shared-group_is_not_g+w/comment_3_621beade26a1dbbdea000ca43d93a325._comment @@ -3,5 +3,12 @@ subject="""comment 3""" date="2021-07-12T14:09:19Z" content=""" -(Fixed the problem with git-annex init's probing.) +Fixed the problem with git-annex init's probing. + +Oh, that's odd, fixing that also fixed the index.lck permissions. + +So, the actual cause of the permissions problem is init deciding to enter +an adjusted unlocked branch. Entering the branch after init does not result +in the problem though. So still need to track down what's happening there, +since it can enter the adjusted branch for other reasons. """]]