From dcf2f7169618aad5b0b31159f219c4e8e07b6021 Mon Sep 17 00:00:00 2001 From: sharad Date: Mon, 17 Feb 2025 19:30:28 +0000 Subject: [PATCH] Added a comment: Faced same issue for long time --- ..._a45af11a7eeb2b7aea2cd6d3580a8c42._comment | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/forum/Assistant___47___watch_doesn__39__t_create_symlinks/comment_1_a45af11a7eeb2b7aea2cd6d3580a8c42._comment diff --git a/doc/forum/Assistant___47___watch_doesn__39__t_create_symlinks/comment_1_a45af11a7eeb2b7aea2cd6d3580a8c42._comment b/doc/forum/Assistant___47___watch_doesn__39__t_create_symlinks/comment_1_a45af11a7eeb2b7aea2cd6d3580a8c42._comment new file mode 100644 index 0000000000..668caa87b6 --- /dev/null +++ b/doc/forum/Assistant___47___watch_doesn__39__t_create_symlinks/comment_1_a45af11a7eeb2b7aea2cd6d3580a8c42._comment @@ -0,0 +1,32 @@ +[[!comment format=mdwn + username="sharad" + avatar="http://cdn.libravatar.org/avatar/0d6c19d5c8f500413f056f94c8c0f308" + subject="Faced same issue for long time" + date="2025-02-17T19:30:27Z" + content=""" + + +Found that + +git annex lock . + + +fix it + + +I guess when copied it kept in unlocked state which may be nothing but absence of symlink (layman term) +So by this logic when I tried +git annex lock . +it fixed this problem. + +Not sure if here are any option/config to control this that +when file first copies it should be directly put into locked state. + + +Thanks + + + + + +"""]]