mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2020-11-09 12:38:44 -04:00
parent dd52d8ebdc
commit 661499732a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
doc/bugs/file_not_correctly_added/comment_4_d0eb0c30db384a1dad7516377f5a069e._comment Normal file
View file

@ -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.
"""]]