From 661499732a9631ceb85e5e6efe494a397536fc45 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 Nov 2020 12:38:44 -0400 Subject: [PATCH] comment --- ..._d0eb0c30db384a1dad7516377f5a069e._comment | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/file_not_correctly_added/comment_4_d0eb0c30db384a1dad7516377f5a069e._comment diff --git a/doc/bugs/file_not_correctly_added/comment_4_d0eb0c30db384a1dad7516377f5a069e._comment b/doc/bugs/file_not_correctly_added/comment_4_d0eb0c30db384a1dad7516377f5a069e._comment new file mode 100644 index 0000000000..6798e541a9 --- /dev/null +++ b/doc/bugs/file_not_correctly_added/comment_4_d0eb0c30db384a1dad7516377f5a069e._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2020-11-09T16:16:31Z" + content=""" +So, the test suite contains many tests that would blow up if it was breaking +this way. + +It seems to me you must have something in your git configuration or other +local environment, or in the repo's git-annex config, that is causing this, +since it doesn't happen to anyone else. Or perhaps something else like a +version of git that is somehow problimatic. + +If annex.addunlocked is configured, `git-annex add` will add the file to +the annex in unlocked mode. This must be happening, because a) the command +does not say "non-large file; adding content to git repository" which it +would if annex.largefiles was configured to make that happen and b) +git-annex lock/unlock only operate on annexed files. + +The thing I don't understand, and cannot reproduce, is that +.git/annex/objects should contain an object after `git-annex add`, and you +show it does not. It seems to me that `git annex whereis` should probably +be either complaining that it's lost the content, or tell about some other +repository that the content has somehow moved to. Or if not, at least `git +annex fsck` should have something to say about this situation. +"""]]