1 ### Please describe the problem.
3 git annex commands with `--all` option in tuned repository (with `annex.tune.branchhash1=true`) do not do anything.
5 ### What steps will reproduce the problem?
7 1. Initialize a tuned annex repository with `git annex init -c annex.tune.branchhash1=true`.
8 2. Add some files to annex.
9 3. Now `git annex whereis --all` and `git annex fsck --all` (and maybe other commands) don't show/do anything.
11 ### What version of git-annex are you using? On what operating system?
13 Version 7.20191230-g985373f8e, compiled from sources, on Debian buster 10.2.
15 ### Please provide any additional information below.
22 Initialized empty Git repository in /home/test/testdir/.git/
24 ~/testdir $ git annex init -c annex.tune.branchhash1=true testrepo
25 init testrepo (scanning for unlocked files...)
27 (recording state in git...)
29 ~/testdir $ echo abcabc >file
31 ~/testdir $ git annex add file
34 (recording state in git...)
36 ~/testdir $ git commit -m file
37 [master (root-commit) b910684] file
38 1 file changed, 1 insertion(+)
39 create mode 120000 file
41 ~/testdir $ git annex whereis
43 67d9c35f-e206-404f-a9da-6c94894a4f9f -- testrepo [here]
46 ~/testdir $ git annex whereis --all
48 ~/testdir $ git annex fsck
49 fsck file (checksum...) ok
50 (recording state in git...)
52 ~/testdir $ git annex fsck --all
53 (recording state in git...)
56 But `--key` option works:
59 ~/testdir $ git annex lookupkey file
60 SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470
62 ~/testdir $ git annex whereis --key SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470
63 whereis SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470 (1 copy)
64 67d9c35f-e206-404f-a9da-6c94894a4f9f -- testrepo [here]
67 ~/testdir $ git annex fsck --key SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470
68 fsck SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470 (checksum...) ok
69 (recording state in git...)
75 ~/testdir $ find .git/annex/objects/ -type f
76 .git/annex/objects/J3/3f/SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470/SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470
78 ~/testdir $ git ls-tree -r git-annex
79 100644 blob 20f9faf7ca569d23da5f106a445609d018fa221d activity.log
80 100644 blob 71f3551b7119daa3c4679d2b790d72b6bc06cbb8 c34/SHA256E-s7--2ed91d820157c0530ffbae54122d998e0de6d958f266b682f7c528942f770470.log
81 100644 blob d475e423f6fb4863559e8cca981ae8a433f68516 difference.log
82 100644 blob bf91bd54df30e28f40b49670cf9c9c26ff600a22 uuid.log
85 ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
87 Of course, I love it! Great project, thanks, Joey!
89 However, /me always wants more features from it. It's great that git-annex continues to develop.