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 2025-05-08 12:41:31 -04:00
parent 13154f5cb2
commit bda9dec2f5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/OsPath_bld_of_g-a_shows_files_needlessly_modified/comment_4_8ceac199ea2b48ef530b0488f1a15ff1._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2025-05-08T16:33:54Z"
content="""
I've reproduced this.
Note that running `git-annex add` on the affected files will clear up the
problem. It manages to restage the file, and as there is no modification,
is otherwise a no-op.
As a first analysis, I looked as annex.debug output between the two
versions of git-annex. There were no differences other than pid numbers and
git-annex branch shas.
Also, after running `git-annex get` with the bad git-annex, running `git
status` with the good git-annex in path did not correct the problem.
My current guess is that restagePointerFiles has changed its behavior in
the filenames it sends to git update-index. In particular the comment about
"update-index is documented as picky" about filepaths suggests a small and
otherwise ok change to a file path could cause this breakage.
"""]]