From 869933877a0f80c8ca580b97d50d1a1d9cc36ba4 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Oct 2019 13:53:07 -0400 Subject: [PATCH] comment --- ..._2_48d27b557d31f25fc4b2fc7e4ef55df3._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__/comment_2_48d27b557d31f25fc4b2fc7e4ef55df3._comment diff --git a/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__/comment_2_48d27b557d31f25fc4b2fc7e4ef55df3._comment b/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__/comment_2_48d27b557d31f25fc4b2fc7e4ef55df3._comment new file mode 100644 index 0000000000..a7ba86abb0 --- /dev/null +++ b/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__/comment_2_48d27b557d31f25fc4b2fc7e4ef55df3._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2019-10-21T17:23:30Z" + content=""" +Hmm, that's a surprising error message to see in this situation. + +It sort of looks like git-annex has been unable to lock the local copy of +the content to indicate that it's in the process of dropping it. I can +reproduce the error message if I purposefully make it not provide a content +removal lock. But, I cannot find a code path where a content removal lock +is not actually provided when dropping from the local repo. +(`Command.Drop.performLocal` always passes `Just contentlock` to `doDrop`.) + +Can you paste a full transcript of this happening so I can be sure I +understand what you're doing and seeing? +"""]]