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

rename forum/why_are_all_those_files_modified.mdwn to bugs/why_are_all_those_files_modified.mdwn

Browse source
This commit is contained in:
anarcat 2018-12-11 17:09:47 +00:00 • committed by admin
parent f226b34b37
commit 5e3323bc4a
7 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/why_are_all_those_files_modified.mdwn Normal file
View file

@ -0,0 +1,20 @@
Following up on [[todo/clarify_that_v7_applies_to_all_clones]], the
next step was to fetch all content from the central, still v5
repository, which worked fine.
But weirdly, some files showed up as modified:
$ git annex get
[...]
$ git status
## master...origin/master
M calendrier/photos/DSCF0879.jpg
M calendrier/photos/DSCF1191.jpg
Strangely, git doesn't see which changes are present here:
$ git diff
[... takes some time, but no output ...]
$
Workaround: `git checkout .` - but I don't understand why that is happening in the first place... Is that a bug? -- [[anarcat]]

11
doc/bugs/why_are_all_those_files_modified/comment_1_2a504fe76dc1715fc8989eeee603c8ab._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-12-04T21:27:30Z"
content="""
If the file is locked, git-annex get has to modify it when it populates it.
git-annex is supposed to restage the file in order to update git's index.
In a few cases where the index file is locked by something else, it is
unable to do so and displays a warning, so perhaps that's what happened here.
"""]]

12
doc/bugs/why_are_all_those_files_modified/comment_2_0774937b43a9bc592f2c1160a0155b49._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="anarcat"
avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
subject="comment 2"
date="2018-12-04T21:37:54Z"
content="""
> If the file is locked, git-annex get has to modify it when it populates it.
>
> git-annex is supposed to restage the file in order to update git's index. In a few cases where the index file is locked by something else, it is unable to do so and displays a warning, so perhaps that's what happened here.
Hmm... I *think* I ran `git annex unlock` on `curie` here, so all files should be unlocked. I don't know what else could be locking the index file and didn't see a warning about it. I've seen a similar situation when upgrading other repositories in the past as well...
"""]]

8
doc/bugs/why_are_all_those_files_modified/comment_3_b5deb8580c5874c50b85fd1c29ed30b3._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="anarcat"
avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
subject="happened again"
date="2018-12-04T22:08:36Z"
content="""
I just did a `git annex upgrade` with (again) 6.20180913-1~bpo9+1 and I am again seeing all files as modified (but diff is empty). No other command was running on the repository that I know of.
"""]]

21
doc/bugs/why_are_all_those_files_modified/comment_4_0d8c289f0f2bbff9158dc1eb6ab05863._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2018-12-11T16:27:27Z"
content="""
I reproduced as follows:
* Have a v7 repository, and unlock a couple of files.
* Clone to a v5 repository.
* Get the files into the v5 repository. (git annex get won't work on the
unlocked files, but you can get --all or copy from the v7 to the v5 or
whatever)
* Upgrade the v5 repository to v7.
Does that sequence match what you were doing? I didn't reproduce the
problem when just upgrading the v5 and then getting the unlocked files into it.
Seems that the upgrade to v7 process, after scanning for and populating
unlocked files, needs to update git's index. I thought it did, but perhaps
I forgot or that is not working.
"""]]

7
doc/bugs/why_are_all_those_files_modified/comment_5_ade6edafc859f53845fef5ba0c92fb1b._comment Normal file
View file

@ -0,0 +1,7 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2018-12-11T17:03:38Z"
content="""
Fixed the problem I described.
"""]]

14
doc/bugs/why_are_all_those_files_modified/comment_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="anarcat"
avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
subject="possibly"
date="2018-12-11T17:06:19Z"
content="""
> Does that sequence match what you were doing? I didn't reproduce the problem when just upgrading the v5 and then getting the unlocked files into it.
I don't *exactly* remember, unfortunately, but that seems likely. It matches my previous comment, which indicates I upgraded to the backport *after* filing the bug report anyways.
> Seems that the upgrade to v7 process, after scanning for and populating unlocked files, needs to update git's index. I thought it did, but perhaps I forgot or that is not working.
Makes sense! :)
"""]]