===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
git-annex-8.20201103/Assistant/Pairing.hs-46-pairMsgAddr :: PairMsg -> SomeAddr
git-annex-8.20201103/Assistant/Pairing.hs:47:pairMsgAddr (PairMsg (Verifiable (_, _, a) _)) = a
git-annex-8.20201103/Assistant/Pairing.hs-48-
##############################################
git-annex-8.20201103/Assistant/Pairing/Network.hs-103-instance ToSomeAddr IPv4 where
git-annex-8.20201103/Assistant/Pairing/Network.hs:104: toSomeAddr (IPv4 a) = IPv4Addr a
git-annex-8.20201103/Assistant/Pairing/Network.hs-105-
git-annex-8.20201103/Assistant/Pairing/Network.hs-106-instance ToSomeAddr IPv6 where
git-annex-8.20201103/Assistant/Pairing/Network.hs:107: toSomeAddr (IPv6 o1 o2 o3 o4) = IPv6Addr (o1, o2, o3, o4)
git-annex-8.20201103/Assistant/Pairing/Network.hs-108-
git-annex-8.20201103/Assistant/Pairing/Network.hs-109-showAddr :: SomeAddr -> HostName
git-annex-8.20201103/Assistant/Pairing/Network.hs:110:showAddr (IPv4Addr a) = show $ IPv4 a
git-annex-8.20201103/Assistant/Pairing/Network.hs:111:showAddr (IPv6Addr (o1, o2, o3, o4)) = show $ IPv6 o1 o2 o3 o4
git-annex-8.20201103/Assistant/Pairing/Network.hs-112-
##############################################
git-annex-8.20201103/CHANGELOG-1377- is configured.
git-annex-8.20201103/CHANGELOG:1378: * External special remotes can now add info to `git annex info $remote`,
git-annex-8.20201103/CHANGELOG-1379- by replying to the GETINFO message.
##############################################
git-annex-8.20201103/Command/EnableTor.hs-91-
git-annex-8.20201103/Command/EnableTor.hs:92: istoraddr (TorAnnex _ _) = True
git-annex-8.20201103/Command/EnableTor.hs-93-
##############################################
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn-2-
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn:3:The install script [[install/Android/git-annex-install]] only adds an entry to `$PATH` which lasts for as long as the shell used for the install. Subsequent launches of termux will not find `git-annex` on the `$PATH`.
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn-4-
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn:5:I'm puzzled why this hasn't been reported before. Is everyone on Android manually running `./git-annex.linux/git-annex ...` each time, or have they manually set up `$PATH` in their Termux shell profile without reporting back to the community, or am I missing something else?
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn-6-
##############################################
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_2_ca7a2b0d05a925e530b637b209f1af34._comment-9-
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_2_ca7a2b0d05a925e530b637b209f1af34._comment:10:The comment near the top even explicitly admits that it doesn't permanently set up `$PATH`:
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_2_ca7a2b0d05a925e530b637b209f1af34._comment-11-
##############################################
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_4_d8cec7fae740e82c5da1da47037e2da6._comment-7- content="""
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_4_d8cec7fae740e82c5da1da47037e2da6._comment:8:Ah, interesting. Very odd that the install script doesn't do that directly. I do have the same contents in my `~/.profile`, but Termux happily ignores it, so `$PATH` is unaltered. Does it really work for you? What version of Termux do you have?
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_4_d8cec7fae740e82c5da1da47037e2da6._comment-9-"""]]
##############################################
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_8_c15caba920b49cebf88ebd36caa053b7._comment-9-
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_8_c15caba920b49cebf88ebd36caa053b7._comment:10:If you're worried about the impact of adding `cp .profile .zprofile` to the install, a reasonable alternative would be to document that the install relies on setting up `$PATH` via `.profile` - this confusion only arose in the first place because that mechanism is somewhat hidden rather than taking place directly in the install script.
git-annex-8.20201103/doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_8_c15caba920b49cebf88ebd36caa053b7._comment-11-"""]]
##############################################
git-annex-8.20201103/doc/bugs/Android_installation_is_missing___36__PATH_setup.mdwn-2-
git-annex-8.20201103/doc/bugs/Android_installation_is_missing___36__PATH_setup.mdwn:3:After following the (new) Android installation instructions, git-annex is not on `$PATH`, therefore literal `git annex` commands fail.
git-annex-8.20201103/doc/bugs/Android_installation_is_missing___36__PATH_setup.mdwn:4:I'm sure this is trivially fixed by enhancing the install script so that it modifies `$PATH` in the termux profile, or similar.
git-annex-8.20201103/doc/bugs/Android_installation_is_missing___36__PATH_setup.mdwn-5-
##############################################
git-annex-8.20201103/doc/bugs/Assistant_has_created_155_semitrusted_repositories/comment_11_cb49edcc8a13928c171a2acdde32dce9._comment-8-
git-annex-8.20201103/doc/bugs/Assistant_has_created_155_semitrusted_repositories/comment_11_cb49edcc8a13928c171a2acdde32dce9._comment:9:```for i in $(seq 0 52); do git show git-annex:uuid.log @{$i} > ~/tmp/uuid.logs/$i; done```
git-annex-8.20201103/doc/bugs/Assistant_has_created_155_semitrusted_repositories/comment_11_cb49edcc8a13928c171a2acdde32dce9._comment-10-
##############################################
git-annex-8.20201103/doc/bugs/Deleting_last_copy_of_files_doesn__39__t_mark_them_dead.mdwn-2-
git-annex-8.20201103/doc/bugs/Deleting_last_copy_of_files_doesn__39__t_mark_them_dead.mdwn:3:In [deleting unwanted files](https://git-annex.branchable.com/tips/deleting_unwanted_files/) it is mentioned that you can use `git annex drop --force $file` to make it go away. But after that when fsck is run it will warn that there are no copies and that it should be marked as dead. And if it's deleted from the branch it will still complain if fsck is run with `--all`.
git-annex-8.20201103/doc/bugs/Deleting_last_copy_of_files_doesn__39__t_mark_them_dead.mdwn-4-
##############################################
git-annex-8.20201103/doc/bugs/Incorrect_install_dir_for_fish_completion.mdwn-4-
git-annex-8.20201103/doc/bugs/Incorrect_install_dir_for_fish_completion.mdwn:5:git-annex installs fish completions to the wrong directory. `$(SHAREDIR)/fish/completions` is the directory documented as being exclusive to completions which are shipped in the fish source code; third-party applications installing their own completions are intended to use `$(SHAREDIR)/fish/vendor_completions.d` instead.
git-annex-8.20201103/doc/bugs/Incorrect_install_dir_for_fish_completion.mdwn-6-
##############################################
git-annex-8.20201103/doc/bugs/Issue_fewer_S3_GET_requests/comment_3_6ccbb1cff7bc6b4640220d98f7ce21c3._comment-8-
git-annex-8.20201103/doc/bugs/Issue_fewer_S3_GET_requests/comment_3_6ccbb1cff7bc6b4640220d98f7ce21c3._comment:9:Yeah, GET of a bucket is doable. Another problem with it though is, if the bucket has a lot of contents, such as many files, or large files split into many chunks, that all has to be buffered in memory or processed as a stream. It would make sense in operations where git-annex knows it wants to check every key in a bucket. `git annex unused --from $s3remote` is the case that springs to mind where it could be quite useful to do that. Integrating it with `get`, not so much.
git-annex-8.20201103/doc/bugs/Issue_fewer_S3_GET_requests/comment_3_6ccbb1cff7bc6b4640220d98f7ce21c3._comment-10-
##############################################
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-19- substr($link,0,1) ^= \" \";
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment:20: system(\"ln\", \"-s\", $dir, $link);
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-21- }
##############################################
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-24- substr($link,1,1) ^= \" \";
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment:25: system(\"ln\", \"-s\", $dir, $link);
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-26- }
##############################################
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-29- substr($link,0,1) ^= \" \";
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment:30: system(\"ln\", \"-s\", $dir, $link);
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-31- substr($link,1,1) ^= \" \";
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment:32: system(\"ln\", \"-s\", $dir, $link);
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-33- substr($link,0,1) ^= \" \";
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment:34: system(\"ln\", \"-s\", $dir, $link);
git-annex-8.20201103/doc/bugs/OSX_case_insensitive_filesystem/comment_7_45e0178ce9598d086f34a89701536eb5._comment-35- }
##############################################
git-annex-8.20201103/doc/bugs/Podcast_filename_encoding_breaks_Android_client.mdwn-31-
git-annex-8.20201103/doc/bugs/Podcast_filename_encoding_breaks_Android_client.mdwn:32:``convmv -f iso-8859-1 -t utf8 $problemfile --notest`` on the laptop fixes the
git-annex-8.20201103/doc/bugs/Podcast_filename_encoding_breaks_Android_client.mdwn-33-filenames and the Android client stops wrecking everything.
##############################################
git-annex-8.20201103/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_6_f9880977cd07ed71e9515c45b10d09c9._comment-13-[pid 23666] socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 17
git-annex-8.20201103/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_6_f9880977cd07ed71e9515c45b10d09c9._comment:14:[pid 23666] connect(17, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(\"127.0.0.53\")}, 16) = 0
git-annex-8.20201103/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_6_f9880977cd07ed71e9515c45b10d09c9._comment-15-```
##############################################
git-annex-8.20201103/doc/bugs/creating_dot-git-as-symlink_workaround_drops_worktree_configuration_from_submodules.mdwn-46-
git-annex-8.20201103/doc/bugs/creating_dot-git-as-symlink_workaround_drops_worktree_configuration_from_submodules.mdwn:47:which reports the workdir of the outer correctly, but reports `$PATH/outer-with-annex/.git/modules/` (which is definitely not a workdir) for the annex.
git-annex-8.20201103/doc/bugs/creating_dot-git-as-symlink_workaround_drops_worktree_configuration_from_submodules.mdwn-48-
##############################################
git-annex-8.20201103/doc/bugs/enable-tor_failing_on_Android/comment_1_7592b563c0ddb338e1f39ff6cf5fa1f0._comment-14-termux has a tor package, and with tor installed that way, its
git-annex-8.20201103/doc/bugs/enable-tor_failing_on_Android/comment_1_7592b563c0ddb338e1f39ff6cf5fa1f0._comment:15:configuration is in `$PREFIX/etc/tor/torrc` in the termux file tree,
git-annex-8.20201103/doc/bugs/enable-tor_failing_on_Android/comment_1_7592b563c0ddb338e1f39ff6cf5fa1f0._comment-16-and is writable by the termux user, without su.
##############################################
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_3_c49df6a33bbf8c3238f5eec1ef3e8152._comment-6- content="""
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_3_c49df6a33bbf8c3238f5eec1ef3e8152._comment:7:I ran into the same problem: assuming I have a repo at \"/mnt/hd/repo\", then `$ cd /; sudo ln -s /mnt/hd/ .; cd /hd/repo; git annex copy --to=someremote ./some-file` exhibits the problem. Thanks!
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_3_c49df6a33bbf8c3238f5eec1ef3e8152._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment-16-This is a very confusing situation, and different ways of getting the current
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment:17:directory give different results in this situation. In particular `$PWD`
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment-18-contains "/hd/repo" while getcwd(3) will return "/tmp/hd/repo". Paths
##############################################
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment-20-
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment:21:It seems that git is looking at `$PWD` to get "/hd/repo" and normalizing
git-annex-8.20201103/doc/bugs/fatal__58___unable_to_normalize_object_directory/comment_5_cb5332119c54764b4ef1e000b3767b0e._comment-22-the relative path via that. So there's no possible relative path
##############################################
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-31-do
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn:32: trueloc=`sed 's/\/annex\/objects\///g' <"$REPLY"`
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-33- # if you had swap files from editors, they may appear here. Fix them in advance.
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-34- # echo "$REPLY"':'$trueloc
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn:35: truefil=`locate $trueloc/$trueloc | grep work.git-copy`
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn:36: mkdir -p $NEWDIR/`dirname $REPLY`
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-37- cp -p $truefil $NEWDIR/$REPLY
##############################################
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-40-
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn:41:The cycle on all files is not a simple "for dir in \`find $1\`" because of possible newlines and spaces in directories. For my directories that worked, but I'm still not sure about possible bugs in that (actually it complains several times, but seems to work). The script doesn't work in sh, but can be launched via e.g.
git-annex-8.20201103/doc/bugs/fix_git-annex_paths___47___objects___40__repository_not_available__41__.mdwn-42-
##############################################
git-annex-8.20201103/doc/bugs/get_-J_from_ssh_remote_tries_to_lock_in_home_directory__63__/comment_2_3f985fc652c9a15b5989cc82cb5da1ad._comment-21-And the git-annex shell command was similarly passed a directory
git-annex-8.20201103/doc/bugs/get_-J_from_ssh_remote_tries_to_lock_in_home_directory__63__/comment_2_3f985fc652c9a15b5989cc82cb5da1ad._comment:22:of `Git.repoPath $ gitConfigRepo $ remoteGitConfig gc`
git-annex-8.20201103/doc/bugs/get_-J_from_ssh_remote_tries_to_lock_in_home_directory__63__/comment_2_3f985fc652c9a15b5989cc82cb5da1ad._comment-23-
##############################################
git-annex-8.20201103/doc/bugs/git-annex__58_____60__socket__58___16__62____58___hPutBuf__58___resource_vanished___40__Broken_pipe__41__/comment_1_e962317a939bf76097ae1a3b53b146e6._comment-12-
git-annex-8.20201103/doc/bugs/git-annex__58_____60__socket__58___16__62____58___hPutBuf__58___resource_vanished___40__Broken_pipe__41__/comment_1_e962317a939bf76097ae1a3b53b146e6._comment:13:One thing you might try is see what is using socket 16 when it's running, assuming the socket will be the same. (Also, if you've had repeated crashes, it would be good to know if it's 16 each time..). You could do this by looking at `/proc/$pid/fd/16` Also, check the old logs, `.git/annex/daemon.log.*`
git-annex-8.20201103/doc/bugs/git-annex__58_____60__socket__58___16__62____58___hPutBuf__58___resource_vanished___40__Broken_pipe__41__/comment_1_e962317a939bf76097ae1a3b53b146e6._comment-14-"""]]
##############################################
git-annex-8.20201103/doc/bugs/git-annex_cannot_connect_to_freenet_cloud___40__webdav__41__/comment_4_7a139eb2c11ab2e32d22ca0f8bb648a5._comment-6-As to where the first byte went, it seems rather suggestive that the part
git-annex-8.20201103/doc/bugs/git-annex_cannot_connect_to_freenet_cloud___40__webdav__41__/comment_4_7a139eb2c11ab2e32d22ca0f8bb648a5._comment:7:of the server's code you pasted earlier reads out `$firstByte`. Perhaps it
git-annex-8.20201103/doc/bugs/git-annex_cannot_connect_to_freenet_cloud___40__webdav__41__/comment_4_7a139eb2c11ab2e32d22ca0f8bb648a5._comment-8-forgot to preserve that first byte in the file.
##############################################
git-annex-8.20201103/doc/bugs/git_annex_import_is_dangerous_if_you_have_unused_objects/comment_5_1e737b740bc7d95f3329e3481d55fd35._comment-7-somewhere in the working tree is that there's no inexpensive way to
git-annex-8.20201103/doc/bugs/git_annex_import_is_dangerous_if_you_have_unused_objects/comment_5_1e737b740bc7d95f3329e3481d55fd35._comment:8:determine that. It would have to run `git log -n1 -S$KEY` for each file.
git-annex-8.20201103/doc/bugs/git_annex_import_is_dangerous_if_you_have_unused_objects/comment_5_1e737b740bc7d95f3329e3481d55fd35._comment-9-That can take quite a long time in repositories with a lot of history.
##############################################
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_6_f63de6fe2f7189c8c2908cc41c4bc963._comment-8-
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_6_f63de6fe2f7189c8c2908cc41c4bc963._comment:9:git-annex would ensure that every directory containing annexed data contains a new symlink `.git-annex` which points to `$git_root/.git/annex`. Then every symlink to an annexed object uses a relative symlink via this: `.git_annex/objects/xx/yy/ZZZZZZZZZZ`. Even though this symlink is relative, moving it to a different directory would not break anything: if the move destination directory already contained other annexed data, it would also already contain `.git-annex` so git-annex wouldn't need to do anything. And if it didn't, git-annex would simply create a new `.git-annex` symlink there.
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_6_f63de6fe2f7189c8c2908cc41c4bc963._comment-10-
##############################################
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_8_6a00500b24ba53248c78e1ffc8d1a591._comment-17- * In either case, git-annex already goes to the trouble of fixing symlinks, and if anything, I *think* this approach would reduce the number of symlinks which need checking (right?)
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_8_6a00500b24ba53248c78e1ffc8d1a591._comment:18:* find `$git_root/foo -follow`, `diff -r` etc. would traverse into `$git_root/.git/annex`
git-annex-8.20201103/doc/bugs/git_rename_detection_on_file_move/comment_8_6a00500b24ba53248c78e1ffc8d1a591._comment-19-
##############################################
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_6_5506dc1b08516677886da4aa97263864._comment-6- content="""
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_6_5506dc1b08516677886da4aa97263864._comment:7:I think that the whole `git show $sha` for each commit will provide useful context.
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_6_5506dc1b08516677886da4aa97263864._comment-8-
##############################################
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_7_073449cc2cb73efd2b2d3d778a5573de._comment-6- content="""
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_7_073449cc2cb73efd2b2d3d778a5573de._comment:7:thanks Joey. i'm sending the output of ```git show $sha``` separately as it contains some non-public data; according to apt/dpkg logs, the rPi was actually using git-annex:armhf 4.20130521 from Debian testing at the time these commits were done. i did in fact install 4.20130709 and then 4.20130723 a couple of days after the issue showed up, but only yesterday i realised that both versions were segfaulting all the time (just invoking ```git-annex``` would segfault); 4.20130521 works reliably, instead (i have just downgraded to test), so my previous question about an interrupted operation possibly causing the metadata corruption is not valid as the git-annex executable in use at the time of the issue was not segfaulting (at least not under every circumstance as the more recent versions *in my setup* - but i'll dig into this separately - probably some library issue or so).
git-annex-8.20201103/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_7_073449cc2cb73efd2b2d3d778a5573de._comment-8-
##############################################
git-annex-8.20201103/doc/bugs/potential_data_loss_after_late_enabling_of_S3_versioning.mdwn-21-immediately set it to untrusted to avoid data loss:
git-annex-8.20201103/doc/bugs/potential_data_loss_after_late_enabling_of_S3_versioning.mdwn:22:`git annex untrust $mys3remotename`
git-annex-8.20201103/doc/bugs/potential_data_loss_after_late_enabling_of_S3_versioning.mdwn-23-
##############################################
git-annex-8.20201103/doc/bugs/regression_-_yt__58___prefix_for___34__regular__34___urls/comment_4_f05e1047c5d22dddba21a9faa3397f0d._comment-5- content="""
git-annex-8.20201103/doc/bugs/regression_-_yt__58___prefix_for___34__regular__34___urls/comment_4_f05e1047c5d22dddba21a9faa3397f0d._comment:6:That one happened with `git annex addurl --fast $url` so a different code
git-annex-8.20201103/doc/bugs/regression_-_yt__58___prefix_for___34__regular__34___urls/comment_4_f05e1047c5d22dddba21a9faa3397f0d._comment-7-path. Had to add a html page check to youtubeDlFileName to fix it.
##############################################
git-annex-8.20201103/doc/bugs/silently_failing_when_attempting_to_add_ignored_files/comment_2_9fe7fd6296db34ee8ee07fe68459e74b._comment-15-
git-annex-8.20201103/doc/bugs/silently_failing_when_attempting_to_add_ignored_files/comment_2_9fe7fd6296db34ee8ee07fe68459e74b._comment:16:Now it automatically adds everything (except dotfiles) when running `git annex add $DIRPATH`.
git-annex-8.20201103/doc/bugs/silently_failing_when_attempting_to_add_ignored_files/comment_2_9fe7fd6296db34ee8ee07fe68459e74b._comment-17-"""]]
##############################################
git-annex-8.20201103/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_2_7d37b8d79fcb6a0edd99e0bd6f2b0515._comment-14-
git-annex-8.20201103/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_2_7d37b8d79fcb6a0edd99e0bd6f2b0515._comment:15:Anyways, to hopefully \"shine the light\", I have managed to reproduce (with up to date snapshot of annex, didn't get there with systemwide older git-annex) on smaug using initially stalling datalad-crawler tests (so 100% reproducible): just login as `test` user to `smaug`. There is a screen session with one shell there with python's PDB where we were waiting for batched process to exit but it didn't; then 2nd one shows `ps auxw -H | grep '^test'`. Please `strace` or inspect anything you might find pertinent (IIRC, raising debug level for datalad, or disabling code tests coverage collection, was making the stall going away). FTR the command is `PATH=~/git-annex/20201005-snapshot/:$PATH DATALAD_LOG_LEVEL=WARNING DATALAD_TESTS_TEMP_KEEP=1 python -m nose -s -v --with-cov --cover-package datalad ../datalad_crawler/dbs/tests/test_files.py ../datalad_crawler/nodes/tests/test_annex.py` and it ends up in pdb (python debugger) if batched annex did not exit although we waited.
git-annex-8.20201103/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_2_7d37b8d79fcb6a0edd99e0bd6f2b0515._comment-16-"""]]
##############################################
git-annex-8.20201103/doc/bugs/standalone_shim_is_segfaulting_if_IFS__61____36____39____92__013__39__/comment_2_2b7afff24ba025fe3e272ff6f607eadf._comment-5- content="""
git-annex-8.20201103/doc/bugs/standalone_shim_is_segfaulting_if_IFS__61____36____39____92__013__39__/comment_2_2b7afff24ba025fe3e272ff6f607eadf._comment:6:Hmm, that patch looks pretty good, but contains a bashism in the `${IFS:-}`
git-annex-8.20201103/doc/bugs/standalone_shim_is_segfaulting_if_IFS__61____36____39____92__013__39__/comment_2_2b7afff24ba025fe3e272ff6f607eadf._comment-7-and I don't actually understand what the point of that is, if seems to
##############################################
git-annex-8.20201103/doc/bugs/tor_setup_needs_a_unique_magic-wormhole_appid.mdwn-6-
git-annex-8.20201103/doc/bugs/tor_setup_needs_a_unique_magic-wormhole_appid.mdwn:7:To tell magic-wormhole to use a different APPID, just do `wormhole --appid=$APPID send ...` or `wormhole --appid=$APPID receive ...`. APPIDs should be unique and scoped to an owner of some sort, so I'd recommend a DNS name or URL-shaped identifier, something like "git-annex.branchable.com/onion-setup". If you add a new distinct mode, one which doesn't interoperate with the current onion-setup mode, you can allocate a new APPID for that mode too (e.g. "git-annex.branchable.com/new-thing-setup").
git-annex-8.20201103/doc/bugs/tor_setup_needs_a_unique_magic-wormhole_appid.mdwn-8-
##############################################
git-annex-8.20201103/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_1_1c0cad1076d5d4d908b8297e7c13ea33._comment-21-
git-annex-8.20201103/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_1_1c0cad1076d5d4d908b8297e7c13ea33._comment:22:Well, `git commit $file` stages any changes to the file's content before
git-annex-8.20201103/doc/bugs/unannex__58___Cannot_proceed_with_uncommitted_changes_staged_in_the_index/comment_1_1c0cad1076d5d4d908b8297e7c13ea33._comment-23-committing. When the file has been unannexed, this stages the entire large
##############################################
git-annex-8.20201103/doc/bugs/very_slow_export_to_directory_special_remote___40__on_USB_drive__41__.mdwn-65-
git-annex-8.20201103/doc/bugs/very_slow_export_to_directory_special_remote___40__on_USB_drive__41__.mdwn:66:I also noticed that the repo that was so slow did not have the `remote.$REMOTE.annex-tracking-branch` config. But I could still run `sync --content` somehow. After adding this config, the last sync actually ran with 2 MB/s but it still wrote in object store format, not as an exported tree.
git-annex-8.20201103/doc/bugs/very_slow_export_to_directory_special_remote___40__on_USB_drive__41__.mdwn-67-
##############################################
git-annex-8.20201103/doc/bugs/zsh_completions_installed_to_location_not_in_fpath.mdwn-2-
git-annex-8.20201103/doc/bugs/zsh_completions_installed_to_location_not_in_fpath.mdwn:3:Installing git-annex via the Makefile results in a zsh completion installed to `$(PREFIX)/$(SHAREDIR)/zsh/vendor-completions`
git-annex-8.20201103/doc/bugs/zsh_completions_installed_to_location_not_in_fpath.mdwn-4-
git-annex-8.20201103/doc/bugs/zsh_completions_installed_to_location_not_in_fpath.mdwn:5:This is not used by zsh, since the builtin zsh fpath is `$(PREFIX)/$(SHAREDIR)/zsh/site-functions` -- as a result, zsh completions do not work.
git-annex-8.20201103/doc/bugs/zsh_completions_installed_to_location_not_in_fpath.mdwn-6-
##############################################
git-annex-8.20201103/doc/design/adjusted_branches.mdwn-239-OTOH, if adjustment #1 is in place and not #2, a file might be renamed in the
git-annex-8.20201103/doc/design/adjusted_branches.mdwn:240:index, and `git annex get $newname` should work. So, it should look at the
git-annex-8.20201103/doc/design/adjusted_branches.mdwn-241-index in that case.
##############################################
git-annex-8.20201103/doc/design/assistant/blog/day_14__thinking_about_syncing.mdwn-20-pushing changes into a non-bare repository; so instead it drops off a new
git-annex-8.20201103/doc/design/assistant/blog/day_14__thinking_about_syncing.mdwn:21:branch in `.git/refs/remotes/$foo/synced/master`. Then when it's run locally
git-annex-8.20201103/doc/design/assistant/blog/day_14__thinking_about_syncing.mdwn-22-it merges that new branch into `master`.
##############################################
git-annex-8.20201103/doc/design/assistant/blog/day_292__bugfixes/comment_2_8c9e5291ceb257f3a938af0ad967c5d7._comment-8-
git-annex-8.20201103/doc/design/assistant/blog/day_292__bugfixes/comment_2_8c9e5291ceb257f3a938af0ad967c5d7._comment:9:The stricter check was implemented in [8c5b1ae1](https://github.com/gitster/git/commit/8c5b1ae1b26a7512eb29e75391b8b24c0d0439e7) for git v1.8.3. Setting `$EMAIL` or running `git -c user.email=foo@bar` should override it.
git-annex-8.20201103/doc/design/assistant/blog/day_292__bugfixes/comment_2_8c9e5291ceb257f3a938af0ad967c5d7._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/design/assistant/blog/day_50__directory_name/comment_1_782cec95a8558a05b2b38a2d2302214d._comment-6- content="""
git-annex-8.20201103/doc/design/assistant/blog/day_50__directory_name/comment_1_782cec95a8558a05b2b38a2d2302214d._comment:7:Please use `$XDG_CONFIG_HOME` and fall back to `~/.config` if that's not defined.
git-annex-8.20201103/doc/design/assistant/blog/day_50__directory_name/comment_1_782cec95a8558a05b2b38a2d2302214d._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/design/assistant/blog/day_76__pairing/comment_1_09665f269343422cd18051fad1a8c19e._comment-13-1. Create a new annex (I used the web app, created an annex at ~/annex)
git-annex-8.20201103/doc/design/assistant/blog/day_76__pairing/comment_1_09665f269343422cd18051fad1a8c19e._comment:14:2. Add box.com as a remote, using encryption (followed <http://git-annex.branchable.com/tips/using_box.com_as_a_special_remote/>, basically `cd ~/annex; git annex initremote box.com type=directory directory=/media/box.com encryption=$GPGID`)
git-annex-8.20201103/doc/design/assistant/blog/day_76__pairing/comment_1_09665f269343422cd18051fad1a8c19e._comment-15-3. copied a file into the annex (ok, I admit, the file was a bit large, 350MB, but still)
##############################################
git-annex-8.20201103/doc/design/assistant/telehash.mdwn-119-* `git annex sync` could also use the running daemon
git-annex-8.20201103/doc/design/assistant/telehash.mdwn:120:* `git-remote-$transport` could use the running daemon
git-annex-8.20201103/doc/design/assistant/telehash.mdwn-121-* c-telehash might end up linked to openssl, which has licence combination
##############################################
git-annex-8.20201103/doc/design/assistant/webapp/comment_4_f4068a7abbb77ba6a3297cbcf1e503e9._comment-8-
git-annex-8.20201103/doc/design/assistant/webapp/comment_4_f4068a7abbb77ba6a3297cbcf1e503e9._comment:9:By the way, if anyone would like to play with the html templates for the webapp, the main html template is `templates/default-layout.hamlet`. Uses a slightly weird template markup, but plain html will also work. And there's also the `static/` directory; every file in there will be compiled directly into the git-annex binary, and is available at `http://localhost:port/static/$file` in the webapp. See the favicon link in `default-layout.hamlet` of how to construct a type-safe link to a static file: `href=@{StaticR favicon_ico}`. That's all you really need to theme the webapp, without doing any real programming!
git-annex-8.20201103/doc/design/assistant/webapp/comment_4_f4068a7abbb77ba6a3297cbcf1e503e9._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn-224-one of the exported trees, or some merge of them or an entirely new tree).
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn:225:The UI to do this can just be another `git annex export $tree --to remote`.
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn-226-To resolve, diff each exported tree in turn against the resolving tree
##############################################
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn-326-
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn:327:It might be nice for `git annex drop $file --from myexport` and
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn:328:`git annex copy $myfile --to export` to work. However, there are some
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes.mdwn-329-very difficult issues in supporting those, and they don't really
##############################################
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes/comment_4_126ee5332ff88b3993d33d59328d4148._comment-10-
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes/comment_4_126ee5332ff88b3993d33d59328d4148._comment:11:`git annex copy $file --to myexport` could perhaps work; the difficulty
git-annex-8.20201103/doc/design/exporting_trees_to_special_remotes/comment_4_126ee5332ff88b3993d33d59328d4148._comment-12-though is, what if you've exported branch foo, and then checked out bar,
##############################################
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn-8-The external special remote program has a name like
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn:9:`git-annex-remote-$bar`. When
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn:10:`git annex initremote foo type=external externaltype=$bar` is run,
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn-11-git-annex finds the appropriate program in PATH.
##############################################
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn-484- program to use such a remote! All they need to do is run:
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn:485: `git annex enableremote $remotename readonly=true`
git-annex-8.20201103/doc/design/external_special_remote_protocol.mdwn-486-
##############################################
git-annex-8.20201103/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment-6-You can find out the size of a key by using
git-annex-8.20201103/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment:7:`git-annex examinekey $key --format='${bytesize}\n'`
git-annex-8.20201103/doc/design/external_special_remote_protocol/comment_30_7d045871f9ebbb89e3f9bbfa28e8468f._comment-8-(There's a --batch option to avoid needing to spin up
##############################################
git-annex-8.20201103/doc/design/iabackup.mdwn-74-3. Client clones its assigned shard git repository,
git-annex-8.20201103/doc/design/iabackup.mdwn:75: runs `git annex init reinit $UUID`.
git-annex-8.20201103/doc/design/iabackup.mdwn-76-
##############################################
git-annex-8.20201103/doc/design/iabackup.mdwn-150-3. Get the git-annex key of the file, and tell git-annex it's been
git-annex-8.20201103/doc/design/iabackup.mdwn:151: lost from the IA, by running in its shard: `setpresentkey $key $iauuid 0`
git-annex-8.20201103/doc/design/iabackup.mdwn-152-4. The next time a client runs `git annex sync --content`, it will notice
##############################################
git-annex-8.20201103/doc/design/iabackup.mdwn-158- (Remember to turn off the fire alarm by running
git-annex-8.20201103/doc/design/iabackup.mdwn:159: `setpresentkey $key $iauuid 1`)
git-annex-8.20201103/doc/design/iabackup.mdwn-160-
##############################################
git-annex-8.20201103/doc/devblog/day_223__partial_commit_problem.mdwn:1:`git commit $some_unlocked_file` seems like a reasonably common thing for
git-annex-8.20201103/doc/devblog/day_223__partial_commit_problem.mdwn-2-someone to do, so it's surprising to find that it's a [[little bit broken|/bugs/modified_permissions_persist_after_unlock__44___commit]],
##############################################
git-annex-8.20201103/doc/devblog/day_275-276__mostly_Windows.mdwn-7-
git-annex-8.20201103/doc/devblog/day_275-276__mostly_Windows.mdwn:8:Added one nice new feature yesterday: `git annex info $dir` now includes a
git-annex-8.20201103/doc/devblog/day_275-276__mostly_Windows.mdwn-9-table of repositories that are storing files in the directory, with their
##############################################
git-annex-8.20201103/doc/devblog/day_321__download_verification/comment_3_fb0ed50c27a493c3494bf2efbf9a9c5d._comment-5- content="""
git-annex-8.20201103/doc/devblog/day_321__download_verification/comment_3_fb0ed50c27a493c3494bf2efbf9a9c5d._comment:6:Nice! I actually had been doing `git annex get $file && git annex fsck $file` in all my scripts already because I had run into an issue where a bad file got replicated everywhere, and the only good copy I had was `drop`ped before I realized. This would have caught it. Thanks!
git-annex-8.20201103/doc/devblog/day_321__download_verification/comment_3_fb0ed50c27a493c3494bf2efbf9a9c5d._comment-7-"""]]
##############################################
git-annex-8.20201103/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment-6- content="""
git-annex-8.20201103/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment:7:I think that there is nothing fundamental about Mac OS X, which would prevent one from making a clean chroot that would work for non-root users. For instance, I believe that jailkit has been reported to work just fine. The problem is that you'll have to rebuild most of the stuff you need from scratch, which is very tedious. Might be easier to find instances where Homebrew has something like -march=native added to the $CFLAGS (not that I particularly fancy Homebrew of all 'missing' package managers on OS X).
git-annex-8.20201103/doc/devblog/day_99__catching_up_again/comment_1_b871bf0606dc29be9b8c2e5dc150f708._comment-8-
##############################################
git-annex-8.20201103/doc/devblog/youtube-dl_day_3/comment_4_d19a698b28a5d6b583c527b9a909370d._comment-9-
git-annex-8.20201103/doc/devblog/youtube-dl_day_3/comment_4_d19a698b28a5d6b583c527b9a909370d._comment:10:```for _id in `youtube-dl 'https://www.youtube.com/watch?v=ps40Uminvno&list=PLWnVxuqvY7Jj2Z8aeR-qKXACCXUN4Ouv_' --get-id` ; do echo \"https://www.youtube.com/watch?v=${_id}\" ; done | git-annex addurl --batch --jobs 2```
git-annex-8.20201103/doc/devblog/youtube-dl_day_3/comment_4_d19a698b28a5d6b583c527b9a909370d._comment-11-
##############################################
git-annex-8.20201103/doc/encryption.mdwn-28-To see what encryption is used for a special remote, run
git-annex-8.20201103/doc/encryption.mdwn:29:`git annex info $remote` and look for a line like:
git-annex-8.20201103/doc/encryption.mdwn-30-
##############################################
git-annex-8.20201103/doc/encryption/comment_8_66e81e89fd483ca95620522b0f63c4fd._comment-9-Barring bugs, adding another gpg key to a hybrid encryption special remote
git-annex-8.20201103/doc/encryption/comment_8_66e81e89fd483ca95620522b0f63c4fd._comment:10:is as simple as `git annex enableremote $theremote keyid+=$newkey`
git-annex-8.20201103/doc/encryption/comment_8_66e81e89fd483ca95620522b0f63c4fd._comment-11-"""]]
##############################################
git-annex-8.20201103/doc/forum/Always_sync_all_content_to_remote/comment_4_3eda671cea0f8869f1aac0194cae7146._comment-24- - Set `git config core.sharedrepository group` on the server repo as described [here](http://git-annex.branchable.com/tips/shared_git_annex_directory_between_multiple_users/) so that the server's files are accessible to other users in the same group.
git-annex-8.20201103/doc/forum/Always_sync_all_content_to_remote/comment_4_3eda671cea0f8869f1aac0194cae7146._comment:25: - I'm not sure if the previous step was doing anything because updated files were still being changed to the server's group. To deal with this, I added `chgrp -R shared \"$(git rev-parse --show-toplevel)\"` to the `annex-content`, `post-receive`, and `post-merge` hooks.
git-annex-8.20201103/doc/forum/Always_sync_all_content_to_remote/comment_4_3eda671cea0f8869f1aac0194cae7146._comment-26-
##############################################
git-annex-8.20201103/doc/forum/Annex_contents_just_disappeared__63__/comment_4_c3625409652bff5f2165260803269a8a._comment-8-
git-annex-8.20201103/doc/forum/Annex_contents_just_disappeared__63__/comment_4_c3625409652bff5f2165260803269a8a._comment:9:I think what I'm going to do now is to just wipe the slate clean and start over again, by using `unannex -fast` on all the files, wiping `.git`, and then adding everything back in using my new default backend of SHA512E. The bigger pain is doing the same thing on all the servers where I have this data (to avoid having to upload it again), but in such a way that I'm not replicating file history. I think I should be able to just clone, `mv $OLDREPO/.git/annex/objects objects`, `git annex add objects`, `git rm -r --cached objects`, and then everything should be good without even needing a new commit on the remote machine, just a git-annex sync.
git-annex-8.20201103/doc/forum/Annex_contents_just_disappeared__63__/comment_4_c3625409652bff5f2165260803269a8a._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/forum/Basic_set_up_with_one_remote/comment_4_62e554a546e4b50d211f5f65446fd289._comment-8-
git-annex-8.20201103/doc/forum/Basic_set_up_with_one_remote/comment_4_62e554a546e4b50d211f5f65446fd289._comment:9:I'm not sure if the `git-annex find` command will work on a bare repo I can't test as all my repos are configured so that I can access the files in a normal way. Running `git-annex whereis $file` on the client should allow you to check if a file has been uploaded.
git-annex-8.20201103/doc/forum/Basic_set_up_with_one_remote/comment_4_62e554a546e4b50d211f5f65446fd289._comment-10-
##############################################
git-annex-8.20201103/doc/forum/Blacklisting_files___40__so_that_they_get_removed_any_time_a_copy_is_found__41__/comment_2_0f2e7cf29ad9d41e0041924e69425050._comment-16-specific files, then you need to use git-annex to drop the content before
git-annex-8.20201103/doc/forum/Blacklisting_files___40__so_that_they_get_removed_any_time_a_copy_is_found__41__/comment_2_0f2e7cf29ad9d41e0041924e69425050._comment:17:you delete the file. You can use `git annex whereis $file` to see everywhere that
git-annex-8.20201103/doc/forum/Blacklisting_files___40__so_that_they_get_removed_any_time_a_copy_is_found__41__/comment_2_0f2e7cf29ad9d41e0041924e69425050._comment:18:the content has gotten to, and then `git annex drop $file --from` each location
git-annex-8.20201103/doc/forum/Blacklisting_files___40__so_that_they_get_removed_any_time_a_copy_is_found__41__/comment_2_0f2e7cf29ad9d41e0041924e69425050._comment-19-(and from the local repository).
##############################################
git-annex-8.20201103/doc/forum/Can_we_have_remotes_that_aren__39__t_tracked__63___/comment_1_35e5a963b9e58ed7773dfcb884f8ecbd._comment-8-
git-annex-8.20201103/doc/forum/Can_we_have_remotes_that_aren__39__t_tracked__63___/comment_1_35e5a963b9e58ed7773dfcb884f8ecbd._comment:9:I will note that if you know the annex.uuid of the previous AAA repository, you can make the new one use that same uuid, just `git config annex.uuid $UUID`. (`git annex fsck --fast` would be a good idea after doing that.)
git-annex-8.20201103/doc/forum/Can_we_have_remotes_that_aren__39__t_tracked__63___/comment_1_35e5a963b9e58ed7773dfcb884f8ecbd._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/forum/Central_server_with_automatically_merged_working_tree.mdwn-24-* Set `git config core.sharedrepository group` for the repository
git-annex-8.20201103/doc/forum/Central_server_with_automatically_merged_working_tree.mdwn:25:* Add `chgrp -R shared "$(git rev-parse --show-toplevel)"` to the `annex-content`, `post-receive`, and `post-merge` hooks, where `shared` is the name of the group that you want to be able to access the server files.
git-annex-8.20201103/doc/forum/Central_server_with_automatically_merged_working_tree.mdwn-26-
##############################################
git-annex-8.20201103/doc/forum/Convert_regular_git-annex_repo_to_a_rsync_repo/comment_2_76bfb11396dc20a5105376b22e7e773b._comment-6- content="""
git-annex-8.20201103/doc/forum/Convert_regular_git-annex_repo_to_a_rsync_repo/comment_2_76bfb11396dc20a5105376b22e7e773b._comment:7:However, if the only problem is that pushing and pulling with a git repository makes `git annex sync` take too long, another option is setting `git config remote.$foo.annex-sync false`. You can still then use git-annex commands to get and push data to the remote, and can even `git annex sync $foo` from time to time, but it won't slow down the normal `git annex sync`.
git-annex-8.20201103/doc/forum/Convert_regular_git-annex_repo_to_a_rsync_repo/comment_2_76bfb11396dc20a5105376b22e7e773b._comment-8-
##############################################
git-annex-8.20201103/doc/forum/Curious_file_in_repository.mdwn-14-
git-annex-8.20201103/doc/forum/Curious_file_in_repository.mdwn:15:Is it something to do with locked/unlocked files? I never unlock anything. `git-annex lock Cats.mkv` changes nothing. `git-annex list` shows no files. `git-annex checkpresentkey $(git-annex calckey Cats.mkv)` returns error number 1. So, it seems safe to say that the file is not in the repository and it _wont't_ go into the repository (not like this). I find this very puzzling!
git-annex-8.20201103/doc/forum/Curious_file_in_repository.mdwn-16-
##############################################
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment-8-
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment:9:Create a text file called `hi.txt` from Termux in `/data/data/com.termux/files/home` AKA `$HOME`. Launch `Turbo Editor` enable `Use the Storage Access Framework` in Preferences menu. Click `Open a file` | `Open from` `Termux`, click `hi.txt`, edit file, save. Now I can see changes in Termux. Nice.
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment-10-
##############################################
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment-12-
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment:13:I wasn't able to find the Termux `$HOME` folder in any File Manager I tried, nor any Gallery App.
git-annex-8.20201103/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment-14-
##############################################
git-annex-8.20201103/doc/forum/Disadvantages_of_WORM__58___long_filename__63__.mdwn-8-
git-annex-8.20201103/doc/forum/Disadvantages_of_WORM__58___long_filename__63__.mdwn:9:`$ git annex copy --to dest Pictures` fails, but `$ cd Pictures/dir_with_problematic_file; git annex copy --to dest .` works.
git-annex-8.20201103/doc/forum/Disadvantages_of_WORM__58___long_filename__63__.mdwn-10-
##############################################
git-annex-8.20201103/doc/forum/Feature_request__58___Multiple_concurrent_transfers.mdwn-11-
git-annex-8.20201103/doc/forum/Feature_request__58___Multiple_concurrent_transfers.mdwn:12: # for j in `seq -w 0 10`; do echo DOING $j; for i in `curl "http://127.0.0.1:$1/?auth=$2" | grep "continue" | gawk -F\" ' { print $8 } '`; do curl "http://127.0.0.1:$1$i"; sleep 0; done; done
git-annex-8.20201103/doc/forum/Feature_request__58___Multiple_concurrent_transfers.mdwn-13-
##############################################
git-annex-8.20201103/doc/forum/File_downloaded_again_and_again/comment_1_666b907935d467d5d7c0e57831d76631._comment-21-Another way to deal with it is to unlock one of the files, and add it back
git-annex-8.20201103/doc/forum/File_downloaded_again_and_again/comment_1_666b907935d467d5d7c0e57831d76631._comment:22:using `git annex add --backend=WORM $file`. This will make git-annex
git-annex-8.20201103/doc/forum/File_downloaded_again_and_again/comment_1_666b907935d467d5d7c0e57831d76631._comment-23-allocate a new key, only for that copy of the file.
##############################################
git-annex-8.20201103/doc/forum/Getting_the_status_of_a_remotely_changed_annex_file/comment_1_e323c21d27bb0946993ba1438429c457._comment-8-
git-annex-8.20201103/doc/forum/Getting_the_status_of_a_remotely_changed_annex_file/comment_1_e323c21d27bb0946993ba1438429c457._comment:9:Or, you can run a command like `git annex whereis $file` and see if it includes \"here\" in the list of locations.
git-annex-8.20201103/doc/forum/Getting_the_status_of_a_remotely_changed_annex_file/comment_1_e323c21d27bb0946993ba1438429c457._comment-10-
##############################################
git-annex-8.20201103/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment-10-
git-annex-8.20201103/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment:11:So, use this to check the PATH that is available on the system: `ssh yourserver 'echo $PATH'`
git-annex-8.20201103/doc/forum/Git_annex_assistant_can__39__t_find_rsync_nor_git-annex_on_server/comment_2_496e2f3a61b609ebb28ab55e5c30022b._comment-12-"""]]
##############################################
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment-15-2. `stat .git/annex/sentinal --terse` and paste the output of that.
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment:16:2. Pick one of the files wrongly showing as modified. Run `stat $file --terse`
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment-17- and paste the output of that.
##############################################
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment-19- Be sure to replace $file with the name of the file:
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment:20: `cat $(git annex find $file --format='.git/annex/objects/${hashdirlower}${key}/${key}.cache`)
git-annex-8.20201103/doc/forum/Git_annex_status_always_showing_annexed_files_as_modified/comment_6_54155343eef8c6f95574dffb3910fc61._comment-21-
##############################################
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment-8-
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment:9:The right answer is probably to run: `git annex drop $file`, with no --numcopies, no --force, etc. Just let git-annex do its job; it will check the remotes to ensure that enough copies of the file exist to make it safe to drop the content of the file from the local repository. (
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment-10-Note that --numcopies=0 is very unsafe, you're asking git-annex to delete even the last copy of your data without checking when you do that.)
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment-11-
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment:12:If your goal is to get rid of every copy of this file from every repository that has a copy, I suggest just `git rm $file; git commit`, followed by running `git annex unused` in the various repositories to clean them up.
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment-13-
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment:14:There is a faster way, which is to run `git annex drop --from $remote` for each remote that has the file. If you want to get rid of every copy of the file, for sure, you could add a --force to that.
git-annex-8.20201103/doc/forum/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment-15-
##############################################
git-annex-8.20201103/doc/forum/How_to_register_arguments_for_an_external_special_remote__63__/comment_6_e0753fef2b93ae5a114894dbdc014ec4._comment-10-
git-annex-8.20201103/doc/forum/How_to_register_arguments_for_an_external_special_remote__63__/comment_6_e0753fef2b93ae5a114894dbdc014ec4._comment:11:Just give me a few days to get it working with `pip` (so people don't have to mess around with their $PATH), document it better, and run `git annex testremote` a bazillion times on it.
git-annex-8.20201103/doc/forum/How_to_register_arguments_for_an_external_special_remote__63__/comment_6_e0753fef2b93ae5a114894dbdc014ec4._comment-12-
##############################################
git-annex-8.20201103/doc/forum/How_to_restore_symlinks/comment_2_f9ec6096595e2c149c48924e3b54542f._comment-8-
git-annex-8.20201103/doc/forum/How_to_restore_symlinks/comment_2_f9ec6096595e2c149c48924e3b54542f._comment:9:For example, you could run `git status` to see if git shows them as recently deleted, and then use `git checkout $file` to restore the deleted files.
git-annex-8.20201103/doc/forum/How_to_restore_symlinks/comment_2_f9ec6096595e2c149c48924e3b54542f._comment-10-
##############################################
git-annex-8.20201103/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_4_07a190aa19006611739cccfc5aac5a6f._comment-7- content="""
git-annex-8.20201103/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_4_07a190aa19006611739cccfc5aac5a6f._comment:8:Thanks. Yes, I have it set to `refuse` globally in `~/.gitconfig`. I definitely don't want to unset it since that could really screw up my working trees. Your idea of disabling localization (`LANG=C` or similar, I guess?) and checking for \"refusing to update checked out branch\" sounds reasonable, but I would prefer a way to just stop it even *trying* to update anything other than `synced/$BRANCH`.
git-annex-8.20201103/doc/forum/Is_it_possible_to_stop_annex_sync_from_trying_to_push_to_checked_out_branches__63__/comment_4_07a190aa19006611739cccfc5aac5a6f._comment-9-"""]]
##############################################
git-annex-8.20201103/doc/forum/Is_there_a_way_to_override_the_import_destination__63__.mdwn-2-
git-annex-8.20201103/doc/forum/Is_there_a_way_to_override_the_import_destination__63__.mdwn:3:(Actually, for my current use case, what I really want is to import a/b/c to $REPO/a/b/c -- but _not_ to import all the rest of the tree under a/. Can't get there either. If I say `git annex import a/b/c`, the directory structure isn't preserved; the file ends up at $REPO/c. For this specific use case, a `--preserve-directories` option to `import` would be splendid, but that's rather specific; being able to specify an arbitrary destination would be a more general solution.)
git-annex-8.20201103/doc/forum/Is_there_a_way_to_override_the_import_destination__63__.mdwn-4-
##############################################
git-annex-8.20201103/doc/forum/Locking_and_then_unlocking_a_file_results_in_file_changed_warning/comment_3_fd39e6ceffd9bf0709658c34945d8699._comment-14-
git-annex-8.20201103/doc/forum/Locking_and_then_unlocking_a_file_results_in_file_changed_warning/comment_3_fd39e6ceffd9bf0709658c34945d8699._comment:15:If you are sure you want to throw away any changes, use --force as suggested. If not, use `git annex add $file`, and assuming you're using a checksumming backend, it will notice the file has not changed and do what you want `git annex lock $file` to have done in this case.
git-annex-8.20201103/doc/forum/Locking_and_then_unlocking_a_file_results_in_file_changed_warning/comment_3_fd39e6ceffd9bf0709658c34945d8699._comment-16-"""]]
##############################################
git-annex-8.20201103/doc/forum/Making_git-annex_less_necessary/comment_4_384813dd022dfd9c1ef14e0f1479a123._comment-10-
git-annex-8.20201103/doc/forum/Making_git-annex_less_necessary/comment_4_384813dd022dfd9c1ef14e0f1479a123._comment:11:*concerning hash sizes or parameterized hashes*: the problems with hash sizes could be avoided if instead of putting the objects in the \"normal\" object dir, barefiles would be managed in a similar way as packs are. when a new files gets added, they'd be cow-copied to ``.git/objects/bare/${HA}/${SH}``, and ``.git/objects/bareprefix/${HA}/${SH}`` would contain the \"blob ${SIZE}\0\" prefix that gets concatenated to the object body to form the object itself.
git-annex-8.20201103/doc/forum/Making_git-annex_less_necessary/comment_4_384813dd022dfd9c1ef14e0f1479a123._comment-12-
##############################################
git-annex-8.20201103/doc/forum/Managing_a_large_number_of_files_archived_on_many_pieces_of_read-only_medium___40__E.G._DVDs__41__/comment_5_49ac298d39c824b0e52a239961463e09._comment-10-
git-annex-8.20201103/doc/forum/Managing_a_large_number_of_files_archived_on_many_pieces_of_read-only_medium___40__E.G._DVDs__41__/comment_5_49ac298d39c824b0e52a239961463e09._comment:11:One option is to use the web special remote, with file:// urls. Assuming a given disc will always end up mounted somewhere stable, such as /media/dvd1, /media/dvd2, etc, you could then just `git annex addurl file:///media/dvd1/$file`. `git annex whereis` will show the url, which has enough info to work out the disk to mount.
git-annex-8.20201103/doc/forum/Managing_a_large_number_of_files_archived_on_many_pieces_of_read-only_medium___40__E.G._DVDs__41__/comment_5_49ac298d39c824b0e52a239961463e09._comment-12-
##############################################
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_1_fffb59ad5a197d2980dd0ec35cf4aafa._comment-6- content="""
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_1_fffb59ad5a197d2980dd0ec35cf4aafa._comment:7:What you describe, `git annex get $file --from remote` silently not doing anything, is the expected behavior if the remote doesn't have the file. This allows you to eg, run `git annex get . --from remote` and get all files that the remote does have while skipping the rest.
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_1_fffb59ad5a197d2980dd0ec35cf4aafa._comment-8-
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_1_fffb59ad5a197d2980dd0ec35cf4aafa._comment:9:Did you ever try looking at `git annex whereis $file` ?
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_1_fffb59ad5a197d2980dd0ec35cf4aafa._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_2_0cfcc2075bff556b9fde5acc3dc1d599._comment-6- content="""
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_2_0cfcc2075bff556b9fde5acc3dc1d599._comment:7:When I run `git annex whereis $file` it tells me it's available at box, s3, my rsync remote, the original repo (from the machine I created the annex on), and my temporary usb stick repo (nothing wrong with redundancy...). So it seems that git annex thinks the file is available in the s3 remote, even though it's refusing to download it.
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_2_0cfcc2075bff556b9fde5acc3dc1d599._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_5_dd66c9ea0c83388f6826751944330d10._comment-6- content="""
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_5_dd66c9ea0c83388f6826751944330d10._comment:7:Yes, when you run `git annex initremote $remotename` with no other parameters, it enables a remote from the stored configuration.
git-annex-8.20201103/doc/forum/Not_sure_how_to_get_my_s3_remote_back/comment_5_dd66c9ea0c83388f6826751944330d10._comment-8-Which does not include `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID`; you need to set those and then
##############################################
git-annex-8.20201103/doc/forum/Photos__44___raw_and_jpeg__58___drop_jpeg_if_raw_is_available/comment_6_a34d404dbecd6730c1cc28af9c0eac26._comment-9- for k in `find . -name \"*.CR2\"`; do
git-annex-8.20201103/doc/forum/Photos__44___raw_and_jpeg__58___drop_jpeg_if_raw_is_available/comment_6_a34d404dbecd6730c1cc28af9c0eac26._comment:10: if [ -e `dirname $k`/`basename $k .CR2`.JPG ]; then
git-annex-8.20201103/doc/forum/Photos__44___raw_and_jpeg__58___drop_jpeg_if_raw_is_available/comment_6_a34d404dbecd6730c1cc28af9c0eac26._comment-11- <set metadata>
##############################################
git-annex-8.20201103/doc/forum/Possible_bug_in_setting_up_Rsync.net_remote.mdwn-13-
git-annex-8.20201103/doc/forum/Possible_bug_in_setting_up_Rsync.net_remote.mdwn:14:I think the bug is in `${git-annex-root}/Assistant/Ssh.hs` or `${git-annex-root}/Assistant/Pairing/MakeRemote.hs`. The `.2D` and `.2E` bits in the mangled string make me think that the `-` and `.` characters in my hostname are being replaced by some Haskell representation of those values (`2D` in hexadecimal in ASCII is `-`, `2E` is `.`).
git-annex-8.20201103/doc/forum/Possible_bug_in_setting_up_Rsync.net_remote.mdwn-15-
##############################################
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn-4-
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn:5:I saw this in the `git revert` docs and thought that `git annex proxy -- git checkout annex/direct/master~$depth -- $filename` might best suit my needs of restoring a previous version of a file. (I liked the idea of presenting the user with a depth rather than a hash.)
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn-6-
##############################################
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn-10-
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn:11:So annex, thorough as it is, creates a `$filename.variant-local.$ext` file after the auto conflict resolution to preserve the original. `git revert` is neater, history wise, because there is no conflict as git knows exactly what's changing and from whence it came, rather than just some new file content showing up from who knows where with `git checkout`.
git-annex-8.20201103/doc/forum/Proper_usage_of_git_annex_proxy_to_mimc_undo_--depth.mdwn-12-
##############################################
git-annex-8.20201103/doc/forum/Recovering_data_from_rsync_special_remote_after_git-annex-forget/comment_1_265563f95a8ec5918314afc7e6226b56._comment-6- content="""
git-annex-8.20201103/doc/forum/Recovering_data_from_rsync_special_remote_after_git-annex-forget/comment_1_265563f95a8ec5918314afc7e6226b56._comment:7:I think `git annex fsck --fast --from $remote` will make the local annex relearn all the files the remote has without transferring them.
git-annex-8.20201103/doc/forum/Recovering_data_from_rsync_special_remote_after_git-annex-forget/comment_1_265563f95a8ec5918314afc7e6226b56._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment-8-
git-annex-8.20201103/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment:9:The best way to debug it further is probably to run `git annex copy --to $remote` at the command line, passing the name of your remote repository. See if it also stalls there. If so, add a --debug and you can see the actual rsync commands it's using, and perhaps work out the problem from there.
git-annex-8.20201103/doc/forum/SSH_remote_transfers_queued_but_no_movement/comment_1_fea4e2317f850d6166480cddba088ae5._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/forum/Shared_pubkeys__58___decrypting_files_in_special_remotes_without_git-annex/comment_3_9852ed3def9f7c73924d8be88b8581e5._comment-8-
git-annex-8.20201103/doc/forum/Shared_pubkeys__58___decrypting_files_in_special_remotes_without_git-annex/comment_3_9852ed3def9f7c73924d8be88b8581e5._comment:9:Have you tried looking at the generated cipher? `git show git-annex:remote.log | grep 'name='\"your-remote-name \"`? Did you try adding `IFS= read -rd '' cipher < <( printf \"$cipher\n\" )`?
git-annex-8.20201103/doc/forum/Shared_pubkeys__58___decrypting_files_in_special_remotes_without_git-annex/comment_3_9852ed3def9f7c73924d8be88b8581e5._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/forum/Store_annexed_files_encrypted_on_special_remote_with_gcrypt.mdwn-5-- First I set up the external git repository with `git init --bare /path/to/external`
git-annex-8.20201103/doc/forum/Store_annexed_files_encrypted_on_special_remote_with_gcrypt.mdwn:6:- Second I add the special remote with `git annex initremote encrypted-origin type=gcrypt gitrepo=/path/to/external encryption=hybrid keyid=$keyid`
git-annex-8.20201103/doc/forum/Store_annexed_files_encrypted_on_special_remote_with_gcrypt.mdwn-7-- Then I sync with `git annex sync`
##############################################
git-annex-8.20201103/doc/forum/Unable_to_change_RSS_feeds/comment_2_9ed0f746a199bb0ce474b2e9fa4f0a9e._comment-8-
git-annex-8.20201103/doc/forum/Unable_to_change_RSS_feeds/comment_2_9ed0f746a199bb0ce474b2e9fa4f0a9e._comment:9:I keep a file with a list of podcasts I follow and the relevant (old) URL in it is `https://rss.art19.com/freakonomics-radio`. I import them all with `xargs git annex importfeed --relaxed --fast --template='${feedtitle}/${itempubdate}-${itemtitle}${extension}' < feeds.txt`..
git-annex-8.20201103/doc/forum/Unable_to_change_RSS_feeds/comment_2_9ed0f746a199bb0ce474b2e9fa4f0a9e._comment-10-
##############################################
git-annex-8.20201103/doc/forum/Undo_Git_Annex_Changes_To_Linked_Files/comment_1_568dde820c2608d86d05b07444146a26._comment-8-
git-annex-8.20201103/doc/forum/Undo_Git_Annex_Changes_To_Linked_Files/comment_1_568dde820c2608d86d05b07444146a26._comment:9:`git annex get $file`
git-annex-8.20201103/doc/forum/Undo_Git_Annex_Changes_To_Linked_Files/comment_1_568dde820c2608d86d05b07444146a26._comment:10:`git annex unannex $file`
git-annex-8.20201103/doc/forum/Undo_Git_Annex_Changes_To_Linked_Files/comment_1_568dde820c2608d86d05b07444146a26._comment-11-
##############################################
git-annex-8.20201103/doc/forum/Using_Linux_static_builds/comment_1_22fd266cbe68af3e754a10f1f1295e9b._comment-11-
git-annex-8.20201103/doc/forum/Using_Linux_static_builds/comment_1_22fd266cbe68af3e754a10f1f1295e9b._comment:12:The static build can be used with ssh. The git-annex assistant should set things up properly. If you want to do it by hand, when it does is configure the ssh key to run ~/.ssh/git-annex-shell, and that file is then made a shell script that runs `runshell git-annex-shell -c \"$SSH_ORIGINAL_COMMAND\"`
git-annex-8.20201103/doc/forum/Using_Linux_static_builds/comment_1_22fd266cbe68af3e754a10f1f1295e9b._comment-13-"""]]
##############################################
git-annex-8.20201103/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment-15-You can find out if all files are present on the server by running
git-annex-8.20201103/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment:16:`git annex find --not --in $server` on one of the clients. Any files
git-annex-8.20201103/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment-17-it prints out have not been stored in the server.
##############################################
git-annex-8.20201103/doc/forum/View_special_remote_information__63__/comment_1_7c106e0679890f7279c73b5c52d648e2._comment-5- content="""
git-annex-8.20201103/doc/forum/View_special_remote_information__63__/comment_1_7c106e0679890f7279c73b5c52d648e2._comment:6:Recent versions of git-annex have expanded `git annex info $remote`
git-annex-8.20201103/doc/forum/View_special_remote_information__63__/comment_1_7c106e0679890f7279c73b5c52d648e2._comment-7-to be able to show some info for special remotes. What is
##############################################
git-annex-8.20201103/doc/forum/Where_did_my_files_go__63__/comment_1_3ff3ffa95eb2745ff9ec2a903e071d97._comment-6- content="""
git-annex-8.20201103/doc/forum/Where_did_my_files_go__63__/comment_1_3ff3ffa95eb2745ff9ec2a903e071d97._comment:7:I did a dump of all known files: `$ git annex whereis > ../git-annex-whereis`
git-annex-8.20201103/doc/forum/Where_did_my_files_go__63__/comment_1_3ff3ffa95eb2745ff9ec2a903e071d97._comment-8-No sign of the imported file.
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-20-
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:21:The nightly build of git-annex/assistant from NEST (20140908) only prompts for the base path of the msysgit location and it installs files in `$BASE/bin` and `$BASE/cmd`... I'll try manually copying files post-install to mitigate the path issues described in other posts on this forum.
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-22-
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-31-1. cmd.exe's PATH is not touched.
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:32:2. `$GITBASE/cmd` is added to PATH
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:33:3. `$GITBASE/bin` is added to PATH
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-34-
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-36-
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:37:All I did was copy `$BASE/cmd/git-annex.exe` to `$BASE/bin/git-annex.exe` and now both `git annex` and `git-annex` work in my msysgit "git bash" console. I didn't test `cmd.exe` since I selected option 1 in the msysgit installer.
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-38-
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-44-
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:45:## `$HOME` defaulted to some mapped drive, whoops!
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-46-
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-50-
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:51:Oh goodness, the test is reading and writing to my "home directory": a remote filesystem I never use. It's slow. I'll have to configure msysgit to use a different, more local `$HOME`. This a common problem on this workstation. I'll let the test finish in case it reveals something useful to you, but this will not be how I use it going forward...
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-52-
##############################################
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-69-
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn:70:## test results with local NTFS `$HOME`
git-annex-8.20201103/doc/forum/Windows_installation_notes.mdwn-71-
##############################################
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-33- exec 3<index
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment:34: while read key name <&3; do ln -s `git annex examinekey --format='.git/annex/objects/${hashdirmixed}${key}/${key}' \"$key\"` \"$name\"; git add \"$name\"; done
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-35- git commit -m'Import ddar repository contents'
##############################################
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-43-
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment:44: uuid=`git config remote.\"$remote_name\".annex-uuid`
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment:45: now=`printf %6fs $(date +%s)`
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-46-
##############################################
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-50- exec 3<index
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment:51: while read key name <&3; do log=`git annex examinekey --format='${hashdirlower}${key}.log' \"$key\"`; mkdir -p `dirname \"$log\"`; echo \"$now 1 $uuid\" >> \"$log\";git add \"$log\";done
git-annex-8.20201103/doc/forum/__34__Preseeding__34___a_special_remote/comment_2_5e63f5e6f45c11cc86b293ce8acad77f._comment-52- exec 3<&-
##############################################
git-annex-8.20201103/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo/comment_4_a4fd212cb066cd53d0d66eb09f3b39a8._comment-10-
git-annex-8.20201103/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo/comment_4_a4fd212cb066cd53d0d66eb09f3b39a8._comment:11:What but then I wanted to do a one-time sync using rsync. I didnt find out how to tell rsync to follow symlinks at the destination instead of replacing symlinks with normal files. So I first unlocked the 150k emails (which was moderately quick and probably only I/O bound) and then did the rsync using the --checksum option which worked well as well. The problems started when I wanted to lock the whole thing again. This took ages and even after two days it did not output that it was adding files at all. So I used `find -type f | split -a3 -l100` and then `for f in x*; do echo $f; git annex add `echo \`cat $f\``; rm $f; done`. This started off well and I could finally see files being added. Unfortunately when I came back after a couple of hours, the progress slowed down to a crawl of only one file every few seconds.
git-annex-8.20201103/doc/forum/__34__git_annex_lock__34___very_slow_for_big_repo/comment_4_a4fd212cb066cd53d0d66eb09f3b39a8._comment-12-
##############################################
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn-2-
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn:3:``git-annex: ${PATH}/${MYREPO}.git/annex/objects/${HA}/${SH}/SHA1-${HASH}/SHA1-${HASH}: setFileMode: permission denied (Operation not permitted)``
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn-4-
##############################################
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn-10-
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn:11:``[pid 17626] chmod("${FILENAME}", 0100555) = -1 EPERM (Operation not permitted)``
git-annex-8.20201103/doc/forum/__34__permission_denied__34___in_fsck_on_shared_repo.mdwn-12-
##############################################
git-annex-8.20201103/doc/forum/__91__ERROR____93___unknown_archive_format_for_.mat_.tif_and_.json_files.mdwn-6-
git-annex-8.20201103/doc/forum/__91__ERROR____93___unknown_archive_format_for_.mat_.tif_and_.json_files.mdwn:7:```$ datalad download-url --archive url_to_mask.mat```
git-annex-8.20201103/doc/forum/__91__ERROR____93___unknown_archive_format_for_.mat_.tif_and_.json_files.mdwn-8-
##############################################
git-annex-8.20201103/doc/forum/adding_files_without_hashing_them/comment_1_c3113d7aff6b64a325a32b8b281df605._comment-10-
git-annex-8.20201103/doc/forum/adding_files_without_hashing_them/comment_1_c3113d7aff6b64a325a32b8b281df605._comment:11:Or, when you commit a change to a file that had been using WORM, use `git annex add $wormy_file --backend=SHA256E` to make the new version use the better backend.
git-annex-8.20201103/doc/forum/adding_files_without_hashing_them/comment_1_c3113d7aff6b64a325a32b8b281df605._comment-12-"""]]
##############################################
git-annex-8.20201103/doc/forum/annex.largefiles__58___two_quesitons/comment_1_75fc6cd2315e9ad6897b94bcc527ddc1._comment-8-2. If you have a specific file in mind, and it is currently stored in the
git-annex-8.20201103/doc/forum/annex.largefiles__58___two_quesitons/comment_1_75fc6cd2315e9ad6897b94bcc527ddc1._comment:9:annex, you can always `git annex unannex $file` and then `git annex add` it
git-annex-8.20201103/doc/forum/annex.largefiles__58___two_quesitons/comment_1_75fc6cd2315e9ad6897b94bcc527ddc1._comment-10-back, which will re-check the current annex.largefiles configuration.
##############################################
git-annex-8.20201103/doc/forum/bainstorming__58___git_annex_push___38___pull/comment_2_b02ca09914e788393c01196686f95831._comment-6- content="""
git-annex-8.20201103/doc/forum/bainstorming__58___git_annex_push___38___pull/comment_2_b02ca09914e788393c01196686f95831._comment:7:No-so-subtle sarcasm taken and acknowledged :)
git-annex-8.20201103/doc/forum/bainstorming__58___git_annex_push___38___pull/comment_2_b02ca09914e788393c01196686f95831._comment-8-
##############################################
git-annex-8.20201103/doc/forum/big_overhead/comment_7_a762eb55addf81c1c5350c7968598d0f._comment-8-
git-annex-8.20201103/doc/forum/big_overhead/comment_7_a762eb55addf81c1c5350c7968598d0f._comment:9:I can think of one case where this happens when using git-annex at the command line: `git annex add $file; git mv $file other-directory; git commit` will result in a dangling object storing the old symlink target before the file was moved.
git-annex-8.20201103/doc/forum/big_overhead/comment_7_a762eb55addf81c1c5350c7968598d0f._comment-10-
##############################################
git-annex-8.20201103/doc/forum/building_the_standalone_distribution_from_source/comment_13_27f987a16d931a02f5a4ab3f80bf327a._comment-6- content="""
git-annex-8.20201103/doc/forum/building_the_standalone_distribution_from_source/comment_13_27f987a16d931a02f5a4ab3f80bf327a._comment:7:I checked my .bash_history and it was `conda create -n $myname python=3.8` the command used.
git-annex-8.20201103/doc/forum/building_the_standalone_distribution_from_source/comment_13_27f987a16d931a02f5a4ab3f80bf327a._comment-8-
##############################################
git-annex-8.20201103/doc/forum/copy_and_move__63__.mdwn-14-
git-annex-8.20201103/doc/forum/copy_and_move__63__.mdwn:15:In the past, I've just marked files as uploaded by `touch "$media.uploaded"` once my python Flickr script returns a successful error code. But I have no idea how to tell git-annex that this means the file can now be dropped, providing a copy exists on my **2tbusbdrive**.
git-annex-8.20201103/doc/forum/copy_and_move__63__.mdwn-16-
##############################################
git-annex-8.20201103/doc/forum/faking_location_information.mdwn-9-3. initialized the cloned repo with `git annex init "Drive from person X"`
git-annex-8.20201103/doc/forum/faking_location_information.mdwn:10:4. imported the files to the cloned repo with `git annex import --duplicate $path_to_files_from_person_x`
git-annex-8.20201103/doc/forum/faking_location_information.mdwn-11-5. `git annex sync` in the cloned repo
##############################################
git-annex-8.20201103/doc/forum/gadu_-_git-annex_disk_usage/comment_14_d8f69914b88feb3f3ed4f72c26dd74e5._comment-229-
git-annex-8.20201103/doc/forum/gadu_-_git-annex_disk_usage/comment_14_d8f69914b88feb3f3ed4f72c26dd74e5._comment:230:still, it seems to me `git annex info --fast $path` should be more clearly put forward as an alternative du solution for now. maybe this should be made into a tips page?
git-annex-8.20201103/doc/forum/gadu_-_git-annex_disk_usage/comment_14_d8f69914b88feb3f3ed4f72c26dd74e5._comment-231-"""]]
##############################################
git-annex-8.20201103/doc/forum/git-annex-sync_without_syncing_master/comment_2_585648a04a02760a1f16394c00728d79._comment-11-1. union merge any ref with basename `git-annex` onto `git-annex`
git-annex-8.20201103/doc/forum/git-annex-sync_without_syncing_master/comment_2_585648a04a02760a1f16394c00728d79._comment:12:2. union merge `synced/$branch` onto `$branch` where `$branch` is the checked out branch
git-annex-8.20201103/doc/forum/git-annex-sync_without_syncing_master/comment_2_585648a04a02760a1f16394c00728d79._comment-13-
##############################################
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-10-
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn:11:To start with I set up the wiki on the server and git clone to into `$wrkdir` on my laptop. I then initialize a git-annex repo in the `$srcdir` on the server. Leaving the `$gitdir` untouched. The `$scrdir` git-annex repo has to be in `direct` mode. Before doing any syncing I add `annex-ignore = true` and `annex-sync = false` to `.git/config` in the origin repo (`$gitdir`): this is to prevent polluting `$gitdir` with git-annex data. The same process is repeated in the `$wrkdir` on the laptop.
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-12-
##############################################
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-14-
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn:15:With this setup I can then `git add remote $srcdir`, `git add $file` and `git-push` mdwn files and other lightweight data from the laptop. While `git annex-add`, `git-annex sync` and `git-annex copy --to $srcdir` jpg's and other heavy files. All pure git commands work as expected with ikiwiki and the website recompiles etc.
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-16-
##############################################
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-18-
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn:19:I'm frequently left with (non-dangling) symlinks in the `$srcdir` despite the annex repo being in direct mode. When this happens `git-annex fsck` sorts things out.
git-annex-8.20201103/doc/forum/git-annex___38___ikiwiki_experiment.mdwn-20-
##############################################
git-annex-8.20201103/doc/forum/git-annex_across_two_filesystems/comment_1_53167648b8b70b41d19ca662a5f3687e._comment-14-* Use `git annex sync` to keep the git repositories in sync. (Or do it manually with `git pull`)
git-annex-8.20201103/doc/forum/git-annex_across_two_filesystems/comment_1_53167648b8b70b41d19ca662a5f3687e._comment:15:* When you want a file to be available in the local repository, use `git annex get $file` to get it.
git-annex-8.20201103/doc/forum/git-annex_across_two_filesystems/comment_1_53167648b8b70b41d19ca662a5f3687e._comment-16-* When your local repository is getting too full, use `git annex drop` or `git annex move` to flush files
##############################################
git-annex-8.20201103/doc/forum/git-annex_assistant_atempts_to_repair__44___but_never_finishes.mdwn:1:I'm using git-annex (git-annex-6.20160126 from homebrew) on osx and for a while now, it claims that it tries to repair my annex-dir on my osx machine, even though it never finishes (or fails) to do so. I'm not sure what's causing this and I also tried to use `git annex repair`, but this didn't help either (it ran forever but never finishes). I tried to run `git annex fsck` and saw that some larger video files were only in one other place and therefore couldn't be droped, which I think I fixed by doing `git annex add` then `git annex sync` and finally `git annex copy --auto -to $Remote`. I'm not sure how to proceed, the log file doesn't seem to tell me a whole lot either. It just tells me for some of my files "Unable to lock down 1 copy of file that is required to safely drop it." and tries to repair that stuff over and over and over… or at least that's what I guess happens.
##############################################
git-annex-8.20201103/doc/forum/git-annex_tor_remote_not_working.mdwn-12-Using 7.20190819+git2-g908476a9b-1~ndall+1 from neuron's repo.
git-annex-8.20201103/doc/forum/git-annex_tor_remote_not_working.mdwn:13:Still not working and now stuck at `git-annex: tor failed to create hidden service, perhaps the tor service is not running` when doing `sudo git-annex enable-tor $(id -u)`
git-annex-8.20201103/doc/forum/git-annex_tor_remote_not_working.mdwn-14-(and yes, the tor service is indeed running, which make that weird)
##############################################
git-annex-8.20201103/doc/forum/git_annex_get_--want-get_another__95__repo/comment_1_0be0b3981ddd0743ff26cf6d396e521d._comment-12-
git-annex-8.20201103/doc/forum/git_annex_get_--want-get_another__95__repo/comment_1_0be0b3981ddd0743ff26cf6d396e521d._comment:13:Where `$desktop_preferred_content` is whatever files the desktop actually wants on its own, and `$phone_preferred_content` is a copy of the preferred content setting for the phone.
git-annex-8.20201103/doc/forum/git_annex_get_--want-get_another__95__repo/comment_1_0be0b3981ddd0743ff26cf6d396e521d._comment-14-
##############################################
git-annex-8.20201103/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment-9-It is completely normal for git-annex to represent a file whose content is not present in the repository as a broken symlink.
git-annex-8.20201103/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment:10:Typically, git-annex preserves at least one copy of the file in one of your repositories. But if you `git annex add $file; git annex drop --force $file`, you will be left in exactly the situation you describe.
git-annex-8.20201103/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment-11-
git-annex-8.20201103/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment:12:You can use `git annex log $file` to see a log of which repositories contained a copy of the file in the past, and see what times the file was removed from each repository. This might give clues to what operation caused the last copy of the file to be lose.
git-annex-8.20201103/doc/forum/git_annex_on_osx_only_creating_symlinks__63____63__/comment_4_99286f17a87049c303f2aa34c0a90286._comment-13-"""]]
##############################################
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment-23-I am operating in a decentralized fashion. Therefore the error
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment:24:message caused by `git pull $remote` succeeded in encouraging me to
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment:25:instead use `git pull $remote master`, and this excludes the git-annex
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment-26-branch from the fetch. Even worse, a git newbie might realise this
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment:27:and be tempted to do `git pull $remote git-annex`.
git-annex-8.20201103/doc/forum/git_pull_remote_git-annex/comment_4_646f2077edcabc000a7d9cb75a93cf55._comment-28-
##############################################
git-annex-8.20201103/doc/forum/how_to_commit_removed_files_as_repo-droped_entries/comment_2_68392de15bae234de1332b8bc80cc2ff._comment-8-
git-annex-8.20201103/doc/forum/how_to_commit_removed_files_as_repo-droped_entries/comment_2_68392de15bae234de1332b8bc80cc2ff._comment:9:git st -s | grep \"^ D .*\" | tee >(git checkout -- `grep -oE \"\S*$\"`) >(git annex drop `grep -oE \"\S*$\"`)
git-annex-8.20201103/doc/forum/how_to_commit_removed_files_as_repo-droped_entries/comment_2_68392de15bae234de1332b8bc80cc2ff._comment-10-
##############################################
git-annex-8.20201103/doc/forum/how_to_remove_files_and_symlinks_but_keep_historical_file_contents/comment_2_8d99c50fc1347367ccc0714e8d1af385._comment-34-
git-annex-8.20201103/doc/forum/how_to_remove_files_and_symlinks_but_keep_historical_file_contents/comment_2_8d99c50fc1347367ccc0714e8d1af385._comment:35:Or, just make a promise to yourself that you'll never run `git-annex unused`, similarly to how you'd probably never run `rm -rf .git/objects/$rand`, and you don't need the branches; like git, git-annex will retain all data that has ever been checked into it.
git-annex-8.20201103/doc/forum/how_to_remove_files_and_symlinks_but_keep_historical_file_contents/comment_2_8d99c50fc1347367ccc0714e8d1af385._comment-36-
##############################################
git-annex-8.20201103/doc/forum/make___34__git_annex_fsck__34___only_display__44___not_move/comment_1_018cb2fd618a448088d9e91e4872333d._comment-9-in the git repository that linked to it, by running
git-annex-8.20201103/doc/forum/make___34__git_annex_fsck__34___only_display__44___not_move/comment_1_018cb2fd618a448088d9e91e4872333d._comment:10:`git log --stat -S$filename`
git-annex-8.20201103/doc/forum/make___34__git_annex_fsck__34___only_display__44___not_move/comment_1_018cb2fd618a448088d9e91e4872333d._comment-11-"""]]
##############################################
git-annex-8.20201103/doc/forum/not_finding_git-annex-shell_on_remote/comment_1_84881cad02c251a2515cec50fc22bf16._comment-8-
git-annex-8.20201103/doc/forum/not_finding_git-annex-shell_on_remote/comment_1_84881cad02c251a2515cec50fc22bf16._comment:9:in other words paste the following into the very first line of `$HOME/.bashrc`
git-annex-8.20201103/doc/forum/not_finding_git-annex-shell_on_remote/comment_1_84881cad02c251a2515cec50fc22bf16._comment-10-
git-annex-8.20201103/doc/forum/not_finding_git-annex-shell_on_remote/comment_1_84881cad02c251a2515cec50fc22bf16._comment:11:`PATH=$PATH:$HOME/bin:$HOME/bin/git-annex.linux`
git-annex-8.20201103/doc/forum/not_finding_git-annex-shell_on_remote/comment_1_84881cad02c251a2515cec50fc22bf16._comment-12-
##############################################
git-annex-8.20201103/doc/forum/optimising_lookupkey.mdwn:1:to work around [[forum/original_filename_on_s3/]], i need to get the key from a file, and i'm not within the git-annex process. i know there's `git annex lookupkey $FILE`, but that incurs significant overhead because the whole git annex runtime needs to fire up. in my tests, this takes around 25ms on average.
git-annex-8.20201103/doc/forum/optimising_lookupkey.mdwn-2-
##############################################
git-annex-8.20201103/doc/forum/pure_git-annex_only_workflow/comment_3_9b7d89da52f7ebb7801f9ec8545c3aba._comment-6- content="""
git-annex-8.20201103/doc/forum/pure_git-annex_only_workflow/comment_3_9b7d89da52f7ebb7801f9ec8545c3aba._comment:7:Git can actually push into a non-bare repository, so long as the branch you change there is not a checked out one. Pushing into `remotes/$foo/master` and `remotes/$foo/git-annex` would work, however determining the value that the repository expects for `$foo` is something git cannot do on its own. And of course you'd still have to `git merge remotes/$foo/master` to get the changes.
git-annex-8.20201103/doc/forum/pure_git-annex_only_workflow/comment_3_9b7d89da52f7ebb7801f9ec8545c3aba._comment-8-
##############################################
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment-6- content="""
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment:7:To get to a specific version of a file, you need to have a tag or a branch that includes that version of the file. Check out the branch and `git annex get $file`.
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment-8-
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment-9-(Of course, even without a tag or branch, old file versions are retained, unless dropped with `unused`/`dropunused`.
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment:10:So you could even `git checkout $COMMITID`.)
git-annex-8.20201103/doc/forum/retrieving_previous_versions/comment_1_a4e83f688d4ec9177e7bf520f12ed26d._comment-11-"""]]
##############################################
git-annex-8.20201103/doc/forum/syncing_non-git_trees_with_git-annex.mdwn-4-
git-annex-8.20201103/doc/forum/syncing_non-git_trees_with_git-annex.mdwn:5:I've been playing around and arrived at the following setup procedure. For the sake of discussion, I assume that we have two trees `a` and `b` which live in the same directory referred to by `$td`, and that all large files end with the `.avi` suffix.
git-annex-8.20201103/doc/forum/syncing_non-git_trees_with_git-annex.mdwn-6-
##############################################
git-annex-8.20201103/doc/forum/use_case__58___unique_indentifier_of_objets___40__doi_like__41__/comment_1_955f3aac12c1ddb41267c5a23ccb79e3._comment-6- content="""
git-annex-8.20201103/doc/forum/use_case__58___unique_indentifier_of_objets___40__doi_like__41__/comment_1_955f3aac12c1ddb41267c5a23ccb79e3._comment:7:To make git-annex output the key of a file, run: `git annex lookupkey $file`
git-annex-8.20201103/doc/forum/use_case__58___unique_indentifier_of_objets___40__doi_like__41__/comment_1_955f3aac12c1ddb41267c5a23ccb79e3._comment-8-
##############################################
git-annex-8.20201103/doc/forum/views___40__branches__41___never_get_deleted/comment_4_a4764b5bfb08ebe90430ea14fcb6e8e0._comment-6- content="""
git-annex-8.20201103/doc/forum/views___40__branches__41___never_get_deleted/comment_4_a4764b5bfb08ebe90430ea14fcb6e8e0._comment:7:`git annex drop --force $file; git rm $file`
git-annex-8.20201103/doc/forum/views___40__branches__41___never_get_deleted/comment_4_a4764b5bfb08ebe90430ea14fcb6e8e0._comment-8-
##############################################
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn-11-Be
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn:12:`hiddenServiceSocketFile=/var/lib/tor-annex/$(id -u)_$(git config --get annex.uuid)/s`
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn-13-
##############################################
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn-15-
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn:16: `mkdir -p $(dirname $hiddenServiceSocketFile)`
git-annex-8.20201103/doc/forum/walkthrough_report_setting_up_tor_p2p_remote.mdwn-17-
##############################################
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment-30- cd $dir
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment:31: PID=`$DAEMON > /dev/null 2>&1 & echo $!`
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment-32- #echo \"Saving PID\" $PID \" to \" $PIDFILE
##############################################
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment-44- for PID in $(cat $PIDFILE); do
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment:45: if [ -z \"`ps axf | grep ${PID} | grep -v grep`\" ]; then
git-annex-8.20201103/doc/forum/webapp_listen_port_with_autostart/comment_2_39664f833dedc1a4fe083eec9bc4a7cd._comment-46- printf \"%s\n\" \"Process dead but pidfile exists\"
##############################################
git-annex-8.20201103/doc/git-annex-addurl.mdwn-116- content if the file does not yet exist; the same as
git-annex-8.20201103/doc/git-annex-addurl.mdwn:117: `git annex addurl $url --file $file`
git-annex-8.20201103/doc/git-annex-addurl.mdwn-118-
##############################################
git-annex-8.20201103/doc/git-annex-find.mdwn-51-
git-annex-8.20201103/doc/git-annex-find.mdwn:52: The default output format is the same as `--format='${file}\\n'`
git-annex-8.20201103/doc/git-annex-find.mdwn-53-
##############################################
git-annex-8.20201103/doc/git-annex-importfeed/comment_3_bce2b233e4d42fc87a2e17d51e2c2606._comment-5- content="""
git-annex-8.20201103/doc/git-annex-importfeed/comment_3_bce2b233e4d42fc87a2e17d51e2c2606._comment:6:I just thought it was surprising behavior, especially when ```git-annex addurl --file 123-45.ext $url``` preserves the dash in the filename, yet the rss I constructed to add multiple urls, with files, didn't do this.
git-annex-8.20201103/doc/git-annex-importfeed/comment_3_bce2b233e4d42fc87a2e17d51e2c2606._comment-7-
##############################################
git-annex-8.20201103/doc/git-annex-initremote.mdwn-85-
git-annex-8.20201103/doc/git-annex-initremote.mdwn:86: To encrypt to a GPG key, use `encryption=hybrid keyid=$keyid ...`
git-annex-8.20201103/doc/git-annex-initremote.mdwn-87- and fill in the GPG key id (or an email address associated with a GPG key).
##############################################
git-annex-8.20201103/doc/git-annex-preferred-content.mdwn-162- The name of the directory can be configured using
git-annex-8.20201103/doc/git-annex-preferred-content.mdwn:163: `git annex enableremote $remote preferreddir=$dirname`
git-annex-8.20201103/doc/git-annex-preferred-content.mdwn-164-
##############################################
git-annex-8.20201103/doc/git-annex-shell.mdwn-174-replaced with your SSH key. The above also assumes `git-annex-shell`
git-annex-8.20201103/doc/git-annex-shell.mdwn:175:is available in your `$PATH`, use an absolute path if it is not the
git-annex-8.20201103/doc/git-annex-shell.mdwn-176-case. Also note how the above uses the `restrict` option instead of an
##############################################
git-annex-8.20201103/doc/install/OSX/old_comments/comment_10_4d15bfc4fc26e7249953bebfbb09e0aa._comment-9-* `cabal install c2hs`
git-annex-8.20201103/doc/install/OSX/old_comments/comment_10_4d15bfc4fc26e7249953bebfbb09e0aa._comment:10:* add `$HOME/.cabal/bin` to my `$PATH` (so that c2hs program can be found)
git-annex-8.20201103/doc/install/OSX/old_comments/comment_10_4d15bfc4fc26e7249953bebfbb09e0aa._comment-11-"""]]
##############################################
git-annex-8.20201103/doc/install/OSX/old_comments/comment_4_e6109a964064a2a799768a370e57801d._comment-16-1. Download [Ghc 7.4](http://www.haskell.org/ghc/download).
git-annex-8.20201103/doc/install/OSX/old_comments/comment_4_e6109a964064a2a799768a370e57801d._comment:17:2. Run `sudo cabal install git-annex --bindir=$HOME/bin`.
git-annex-8.20201103/doc/install/OSX/old_comments/comment_4_e6109a964064a2a799768a370e57801d._comment-18-3. Compilation of the Crypto-4.2.4 dependency failed since it's not updated to work with Ghc 7.4. You need to patch SHA2.hs (steps below).
git-annex-8.20201103/doc/install/OSX/old_comments/comment_4_e6109a964064a2a799768a370e57801d._comment:19:4. Run `sudo cabal install git-annex --bindir=$HOME/bin` a second time.
git-annex-8.20201103/doc/install/OSX/old_comments/comment_4_e6109a964064a2a799768a370e57801d._comment-20-
##############################################
git-annex-8.20201103/doc/install/OSX/old_comments/comment_5_50777853f808d57b957f8ce9a0f84b3d._comment-6- content="""
git-annex-8.20201103/doc/install/OSX/old_comments/comment_5_50777853f808d57b957f8ce9a0f84b3d._comment:7:If you're missing the `sha256sum` command with Homebrew, it's provided by `coreutils`. You have to change your `$PATH` before running `cabal install git-annex.cabal`:
git-annex-8.20201103/doc/install/OSX/old_comments/comment_5_50777853f808d57b957f8ce9a0f84b3d._comment-8-
##############################################
git-annex-8.20201103/doc/install/fromsource/comment_20_0f553be2a4c666e3bed58b2bce549406._comment-6- content="""
git-annex-8.20201103/doc/install/fromsource/comment_20_0f553be2a4c666e3bed58b2bce549406._comment:7:What is the best way to update git-annex and the dependencies via cabal? Just the `$ cabal install *` commands again?
git-annex-8.20201103/doc/install/fromsource/comment_20_0f553be2a4c666e3bed58b2bce549406._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/install/fromsource/comment_66_849c4c2cfc34991c13d55495e391cce3._comment-44-
git-annex-8.20201103/doc/install/fromsource/comment_66_849c4c2cfc34991c13d55495e391cce3._comment:45:1. Hack the Makefile -- add another `if [ $BUILDER = stack ]` section
git-annex-8.20201103/doc/install/fromsource/comment_66_849c4c2cfc34991c13d55495e391cce3._comment-46-
##############################################
git-annex-8.20201103/doc/metadata.mdwn-32- being.
git-annex-8.20201103/doc/metadata.mdwn:33:* `$field-lastchanged` - This is automatically maintained for each
git-annex-8.20201103/doc/metadata.mdwn-34- field that's set, and gives the date and time of the most recent
##############################################
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-36-
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn:37:`not (inallgroup=client and copies=client:2) and ($client)`
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-38-
##############################################
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-109-
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn:110:`present and ($client)`
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-111-
##############################################
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-124-The name of the directory can be configured using
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn:125:`git annex enableremote $remote preferreddir=$dirname`
git-annex-8.20201103/doc/preferred_content/standard_groups.mdwn-126-
##############################################
git-annex-8.20201103/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment-6- content="""
git-annex-8.20201103/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment:7:You can enable a special remote on a clone by running `git annex enableremote $name`, where $name is the name you used to originally create the special remote. (Older versions of git-annex used `git annex initremote` to enable the special remote on the clone.)
git-annex-8.20201103/doc/special_remotes/S3/comment_10_c366f020c9b97a365e21878a33360079._comment-8-
##############################################
git-annex-8.20201103/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment-12-using a gpg key, with `encryption=shared keyid=whatever`, you'll of course
git-annex-8.20201103/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment:13:also need that gpg key to to use it. If you run `git annex info $myremote`
git-annex-8.20201103/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment-14-it will tell you amoung other things, any gpg keys that are used by that
##############################################
git-annex-8.20201103/doc/special_remotes/directory/comment_18_1b24ac6abc99e2e4bc8c9f4687c81395._comment-6-The hash directories for a key can be looked up by passing the key to
git-annex-8.20201103/doc/special_remotes/directory/comment_18_1b24ac6abc99e2e4bc8c9f4687c81395._comment:7:`git annex examinekey --format '${hashdirlower}\n'`
git-annex-8.20201103/doc/special_remotes/directory/comment_18_1b24ac6abc99e2e4bc8c9f4687c81395._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/special_remotes/directory/comment_4_f5e9b0b477c4e521f8633fd274757fa3._comment-6- content="""
git-annex-8.20201103/doc/special_remotes/directory/comment_4_f5e9b0b477c4e521f8633fd274757fa3._comment:7:The best way to remove a special remote is to first `git annex move --from $remote` to get all the content out of it, then `git annex dead $remote` and finally you can `git remote rm $remote`
git-annex-8.20201103/doc/special_remotes/directory/comment_4_f5e9b0b477c4e521f8633fd274757fa3._comment-8-"""]]
##############################################
git-annex-8.20201103/doc/special_remotes/external.mdwn-12-
git-annex-8.20201103/doc/special_remotes/external.mdwn:13:* All you need is to make a program with a name like `git-annex-remote-$bar`.
git-annex-8.20201103/doc/special_remotes/external.mdwn-14-* Install it in PATH.
git-annex-8.20201103/doc/special_remotes/external.mdwn:15:* When the user runs `git annex initremote foo type=external externaltype=$bar`,
git-annex-8.20201103/doc/special_remotes/external.mdwn-16- it will use your program.
##############################################
git-annex-8.20201103/doc/special_remotes/hook.mdwn-56-
git-annex-8.20201103/doc/special_remotes/hook.mdwn:57:* `annex.$hooktype-store-hook` - Command run to store a key in the special remote.
git-annex-8.20201103/doc/special_remotes/hook.mdwn-58- `ANNEX_FILE` contains the content to be stored.
git-annex-8.20201103/doc/special_remotes/hook.mdwn-59-
git-annex-8.20201103/doc/special_remotes/hook.mdwn:60:* `annex.$hooktype-retrieve-hook` - Command run to retrieve a key from the special remote.
git-annex-8.20201103/doc/special_remotes/hook.mdwn-61- `ANNEX_FILE` is a file that the retrieved content should be written to.
##############################################
git-annex-8.20201103/doc/special_remotes/hook.mdwn-65-
git-annex-8.20201103/doc/special_remotes/hook.mdwn:66:* `annex.$hooktype-remove-hook` - Command to remove a key from the special remote.
git-annex-8.20201103/doc/special_remotes/hook.mdwn-67-
git-annex-8.20201103/doc/special_remotes/hook.mdwn:68:* `annex.$hooktype-checkpresent-hook` - Command to check if a key is present
git-annex-8.20201103/doc/special_remotes/hook.mdwn-69- in the special remote. Should output the key name to stdout, on its own line,
##############################################
git-annex-8.20201103/doc/sync.mdwn-15-Breitner. The idea is to have a branch `synced/master` (actually,
git-annex-8.20201103/doc/sync.mdwn:16:`synced/$currentbranch`), that is never directly checked out, and serves
git-annex-8.20201103/doc/sync.mdwn-17-as a drop-point for other repositories to use to push changes.
##############################################
git-annex-8.20201103/doc/thanks.mdwn-192-
git-annex-8.20201103/doc/thanks.mdwn:193:These people are just inspiring in their enthusiasm and generosity to this
git-annex-8.20201103/doc/thanks.mdwn-194-project.
##############################################
git-annex-8.20201103/doc/tips/Bup_repositories_in_git-annex.mdwn-11-and make the bup repository a subdirectory of it.²
git-annex-8.20201103/doc/tips/Bup_repositories_in_git-annex.mdwn:12:Then `git annex add $BUP_REPO/objects/packs`, i.e. the location of the large data files (.pack & .par2).
git-annex-8.20201103/doc/tips/Bup_repositories_in_git-annex.mdwn:13:The rest of the bup repository should be tracked by Git (`git add $BUP_REPO`).³
git-annex-8.20201103/doc/tips/Bup_repositories_in_git-annex.mdwn-14-This way the repository stays fully functional.
##############################################
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn-8-<pre>
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn:9:git filter-branch --tree-filter 'for FILE in file1 file2 file3;do if [ -f "$FILE" ] && [ ! -L "$FILE" ];then git rm --cached "$FILE";git annex add "$FILE";ln -sf `readlink "$FILE"|sed -e "s:^../../::"` "$FILE";fi;done' --tag-name-filter cat -- --all
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn-10-</pre>
##############################################
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn-13-<pre>
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn:14:git filter-branch --tree-filter 'for FILE in bigfile1.bin subdir1/bigfile2.bin;do if [ -f "$FILE" ] && [ ! -L "$FILE" ];then git rm --cached "$FILE";git annex add "$FILE";ln -sf `readlink "$FILE"|sed -e "s:^../../::"` "$FILE";fi;done' --tag-name-filter cat -- --all
git-annex-8.20201103/doc/tips/How_to_retroactively_annex_a_file_already_in_a_git_repo.mdwn-15-</pre>
##############################################
git-annex-8.20201103/doc/tips/ZSH_completion.mdwn-4-
git-annex-8.20201103/doc/tips/ZSH_completion.mdwn:5:1. make sure your have Python 3 installed (as `python3` somewhere in your `$PATH`; tested with 3.4, should work with 3.2+)
git-annex-8.20201103/doc/tips/ZSH_completion.mdwn-6-2. get it from [GitHub](https://github.com/Schnouki/git-annex-zsh-completion)
git-annex-8.20201103/doc/tips/ZSH_completion.mdwn:7:3. copy `_git-annex` to somewhere in your `$fpath` (I use `$HOME/.config/zsh/completion`)
git-annex-8.20201103/doc/tips/ZSH_completion.mdwn-8-4. run `autoload -U path/to/_git-annex`
##############################################
git-annex-8.20201103/doc/tips/deleting_unwanted_files.mdwn-34-2. `git annex whereis file`
git-annex-8.20201103/doc/tips/deleting_unwanted_files.mdwn:35:3. `git annex drop --force file --from $repo` repeat for each repository listed by the whereis command
git-annex-8.20201103/doc/tips/deleting_unwanted_files.mdwn-36-4. `rm file; git annex sync`
##############################################
git-annex-8.20201103/doc/tips/downloading_podcasts.mdwn-24-there's a --template option. The default is
git-annex-8.20201103/doc/tips/downloading_podcasts.mdwn:25:`--template='${feedtitle}/${itemtitle}${extension}'`
git-annex-8.20201103/doc/tips/downloading_podcasts.mdwn-26-
##############################################
git-annex-8.20201103/doc/tips/downloading_podcasts/comment_23_62603cda8e581a2eb2cc799dffe8a740._comment-5- content="""
git-annex-8.20201103/doc/tips/downloading_podcasts/comment_23_62603cda8e581a2eb2cc799dffe8a740._comment:6:Using a `--template='${feedtitle}/${itempubdate}-${itemtitle}${extension}'` with a libsyn RSS feed (eg, [Poly Weekly](http://polyweekly.libsyn.com/rss)), I found that `itempubdate` was expanding to \"none\", even though there is a date with each entry in the RSS, eg,
git-annex-8.20201103/doc/tips/downloading_podcasts/comment_23_62603cda8e581a2eb2cc799dffe8a740._comment-7-
##############################################
git-annex-8.20201103/doc/tips/dumb_metadata_extraction_from_xbmc/git-annex-xbmc-playcount.pl-64-sub checkdb() {
git-annex-8.20201103/doc/tips/dumb_metadata_extraction_from_xbmc/git-annex-xbmc-playcount.pl:65: my @lines = `echo 'SELECT playCount, path.strPath, files.strFileName FROM movie JOIN files ON files.idFile=movie.idFile JOIN path ON path.idPath=files.idPath;' | sqlite3 $dbpath`;
git-annex-8.20201103/doc/tips/dumb_metadata_extraction_from_xbmc/git-annex-xbmc-playcount.pl-66- print "# finding files...\n" if $verbose;
##############################################
git-annex-8.20201103/doc/tips/file_manager_integration.mdwn-24-This is set up by git-annex creating a
git-annex-8.20201103/doc/tips/file_manager_integration.mdwn:25:`$XDG_DATA_HOME/kservices5/ServiceMenus/git-annex.desktop` file.
git-annex-8.20201103/doc/tips/file_manager_integration.mdwn-26-
##############################################
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_3._comment-19- for fileOrDir in *; do
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_3._comment:20: nfileOrDir=`echo "$fileOrDir" | sed -e 's/\[//g' -e 's/\]//g' -e 's/ /_/g' -e "s/'//g" `
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_3._comment-21- if [ "$fileOrDir" != "$nfileOrDir" ]; then
##############################################
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_7_347b0186755a809594bd42feda6363e2._comment-8-
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_7_347b0186755a809594bd42feda6363e2._comment:9:However, git does provide a way. Try `git log --stat -S $KEY`
git-annex-8.20201103/doc/tips/finding_duplicate_files/comment_7_347b0186755a809594bd42feda6363e2._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/tips/hashdeep_integration.mdwn-95-substitution above (`sed 's/\.[^,]*,/,/'`). This is necessary because
git-annex-8.20201103/doc/tips/hashdeep_integration.mdwn:96:`${keyname}` includes the file extension which is expected with the
git-annex-8.20201103/doc/tips/hashdeep_integration.mdwn-97-`SHA256E` backend, but it is somewhat inconvenient to deal with. Of
##############################################
git-annex-8.20201103/doc/tips/peer_to_peer_network_with_tor.mdwn-21-* The installation process must make a `wormhole` executable available
git-annex-8.20201103/doc/tips/peer_to_peer_network_with_tor.mdwn:22: somewhere on your `$PATH`. Some distributions may only install executables
git-annex-8.20201103/doc/tips/peer_to_peer_network_with_tor.mdwn-23- which reference the Python version, e.g. `wormhole-2.7`, in which case you
##############################################
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn-37-Each exported file will be available to the public at
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn:38:`http://$BUCKET.s3.amazonaws.com/$FILE`
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn-39-
##############################################
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn-66-By default, there is no index.html file exported, so if you open
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn:67:`http://$BUCKET.s3.amazonaws.com/` in a web browser, you'll see an
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public.mdwn-68-XML document listing the files.
##############################################
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method.mdwn-51-
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method.mdwn:52: key=`git annex lookupkey "$fname"`; sign_s3_url.bash --region 'eu-west-1' --bucket 'mybuck' --file-path $key --aws-access-key-id XX --aws-secret-access-key XX --method 'GET' --minute-expire 10
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method.mdwn-53-
##############################################
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method/comment_4_37405f20da790141187e9f780c999448._comment-7-
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method/comment_4_37405f20da790141187e9f780c999448._comment:8: fname=\"2015/01/04/myfile.pdf\" ; git annex copy --to pubweb $fname; key=`git annex lookupkey \"$fname\"`; git annex examinekey $key --format 'https://www.myweb.com/d/${hashdirlower}${key}/${key}\n'
git-annex-8.20201103/doc/tips/publishing_your_files_to_the_public/old_method/comment_4_37405f20da790141187e9f780c999448._comment-9-
##############################################
git-annex-8.20201103/doc/tips/using_gitolite_with_git-annex.mdwn-82-
git-annex-8.20201103/doc/tips/using_gitolite_with_git-annex.mdwn:83:Set `$GL_ADC_PATH` in `.gitolite.rc`, if you have not already done so.
git-annex-8.20201103/doc/tips/using_gitolite_with_git-annex.mdwn-84-
##############################################
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_12_2ce018f181e039b5dd52e2b712f63eea._comment-5- content="""
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_12_2ce018f181e039b5dd52e2b712f63eea._comment:6:You can see the url(s) of a file when you run `git annex whereis $file`
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_12_2ce018f181e039b5dd52e2b712f63eea._comment-7-"""]]
##############################################
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_4_c1133a524989a940f1b5db588707157a._comment-6- content="""
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_4_c1133a524989a940f1b5db588707157a._comment:7:You can use `git annex rmurl $file $url`, which I just added to git-annex.
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_4_c1133a524989a940f1b5db588707157a._comment-8-
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_4_c1133a524989a940f1b5db588707157a._comment:9:(Also, `git annex drop $file --from web` will remove all the urls..)
git-annex-8.20201103/doc/tips/using_the_web_as_a_special_remote/comment_4_c1133a524989a940f1b5db588707157a._comment-10-"""]]
##############################################
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn-14-* Preserve your git configuration changes, and the `annex.uuid` setting:
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn:15: `mv $bad/.git/config $good/.git/config`
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn-16-* Move annexed data into the new repository: `mkdir $good/.git/annex; mv
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn-17- $bad/.git/annex/objects $good/.git/annex/objects`
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn:18:* Reinitalize git-annex: `cd $good; git annex init`
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn:19:* Check for any problems with the annexed data: `cd $good; git annex fsck`
git-annex-8.20201103/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn-20-* Now you can remove the corrupted repository, the new one is ready to use.
##############################################
git-annex-8.20201103/doc/todo/Allow_for_TRANSFER-SUCCESS_to_report_also_a_URL_where_key_could_now_be_obtained_from/comment_3_f667aa26dadadede318d31176292102d._comment-17-
git-annex-8.20201103/doc/todo/Allow_for_TRANSFER-SUCCESS_to_report_also_a_URL_where_key_could_now_be_obtained_from/comment_3_f667aa26dadadede318d31176292102d._comment:18:So, what you can do is run `git annex setpresentkey $key 00000000-0000-0000-0000-000000000001`
git-annex-8.20201103/doc/todo/Allow_for_TRANSFER-SUCCESS_to_report_also_a_URL_where_key_could_now_be_obtained_from/comment_3_f667aa26dadadede318d31176292102d._comment-19-to make it think the web special remote has the url after `SETURLPRESENT`.
##############################################
git-annex-8.20201103/doc/todo/Bittorrent-like_features.mdwn-61-
git-annex-8.20201103/doc/todo/Bittorrent-like_features.mdwn:62:This way, a torrent would just become another source for a specific file. When we `get` the file, it fires up `$YOUR_FAVORITE_TORRENT_CLIENT` to download the file.
git-annex-8.20201103/doc/todo/Bittorrent-like_features.mdwn-63-
##############################################
git-annex-8.20201103/doc/todo/Speed_up___39__import_--clean-duplicates__39__.mdwn-2-
git-annex-8.20201103/doc/todo/Speed_up___39__import_--clean-duplicates__39__.mdwn:3:To do this, I am running `git annex import --clean--duplicates $PATH` on the directories I want to clear out but sometimes, this takes a unnecessarily long time.
git-annex-8.20201103/doc/todo/Speed_up___39__import_--clean-duplicates__39__.mdwn-4-
##############################################
git-annex-8.20201103/doc/todo/append-only_mode/comment_1_eaa7ae80c3758bccd23c4e0a8d1eefc4._comment-9-
git-annex-8.20201103/doc/todo/append-only_mode/comment_1_eaa7ae80c3758bccd23c4e0a8d1eefc4._comment:10:How could this be integrated with gitolite? Should the `if ( can_write($repo) )` branch be amended by a check for the \"+\" flag ([short documentation](http://gitolite.com/gitolite/conf-2/) says that \"RW\" is roughly \"create or fast-forward, no deletes\" while \"RW+\" includes deletes and non-fast-forwards)?
git-annex-8.20201103/doc/todo/append-only_mode/comment_1_eaa7ae80c3758bccd23c4e0a8d1eefc4._comment-11-
##############################################
git-annex-8.20201103/doc/todo/bittorrent__58___support_offline_operation_and_verification.mdwn-53-
git-annex-8.20201103/doc/todo/bittorrent__58___support_offline_operation_and_verification.mdwn:54:* before adding the `timestamp 1 $URL#n` line to the .log.web records of a
git-annex-8.20201103/doc/todo/bittorrent__58___support_offline_operation_and_verification.mdwn-55- locally present file, check against the hashes from the torrent. (this may
##############################################
git-annex-8.20201103/doc/todo/document_git-annex_dependencies/comment_1_bb9cbd703e57adb9ca45e2cea94308a0._comment-9-As far as exactly where each is used, that's pretty easy to grep the code
git-annex-8.20201103/doc/todo/document_git-annex_dependencies/comment_1_bb9cbd703e57adb9ca45e2cea94308a0._comment:10:for (search for `"$command"`) and would be a lot of documentation to write
git-annex-8.20201103/doc/todo/document_git-annex_dependencies/comment_1_bb9cbd703e57adb9ca45e2cea94308a0._comment-11-and keep up to date.
##############################################
git-annex-8.20201103/doc/todo/git-annex-inprogress_--key.mdwn-7-
git-annex-8.20201103/doc/todo/git-annex-inprogress_--key.mdwn:8:A workaround is running `git annex inprogress --all | grep $KEY`, but that's probably relying on an implementation detail that could be changed at any time (though it probably won't as to avoid race conditions as in `tail -f $(git annex inprogress file-thats-almost.done)`).
git-annex-8.20201103/doc/todo/git-annex-inprogress_--key.mdwn-9-
##############################################
git-annex-8.20201103/doc/todo/git_annex_open.mdwn-3-* if the file is already present locally: just `xdg-open` it
git-annex-8.20201103/doc/todo/git_annex_open.mdwn:4:* if it is not present and cannot be streamed: `git annex get "$@" && xdg-open "$@"`
git-annex-8.20201103/doc/todo/git_annex_open.mdwn:5:* if it can be streamed: `git annex get "$@"` and `xdg-open` when enough content has been streamed that we are confident it will play completely (unless network conditions change)
git-annex-8.20201103/doc/todo/git_annex_open.mdwn-6-
##############################################
git-annex-8.20201103/doc/todo/hidden_files.mdwn:1:Add a `git annex hide $file` that behaves like drop, checking counter info
git-annex-8.20201103/doc/todo/hidden_files.mdwn-2-and updating location log to say the current repo no longer has a file --
##############################################
git-annex-8.20201103/doc/todo/import_tree_from_rsync_special_remote.mdwn-14-* listing contents: Using rsync would involve a command like
git-annex-8.20201103/doc/todo/import_tree_from_rsync_special_remote.mdwn:15: `rsync --checksum -avz -i --dry-run --out-format='%C %l %M %f\n' $rsync-url empty-directory`;
git-annex-8.20201103/doc/todo/import_tree_from_rsync_special_remote.mdwn-16- that makes the remote rsync checksum all the files, which could be very
##############################################
git-annex-8.20201103/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__/comment_1_8a59da3012b9d177b4baa72610b72fc9._comment-22-set `ANNEX_GCONV_PATH`, and the wrapper scripts have
git-annex-8.20201103/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__/comment_1_8a59da3012b9d177b4baa72610b72fc9._comment:23:`GCONV_PATH="$ANNEX_GCONV_PATH"`.
git-annex-8.20201103/doc/todo/restore_original_environment_when_running_external_special_remotes_from_standalone_git-annex__63__/comment_1_8a59da3012b9d177b4baa72610b72fc9._comment-24-
##############################################
git-annex-8.20201103/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_4_a765e998ffaecc2af681947263cd80d7._comment-11-1. commit any changes (presumably something like `commit -am 'some default message?'`)
git-annex-8.20201103/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_4_a765e998ffaecc2af681947263cd80d7._comment:12:2. fetch and merge `synced/$(currentbranch)` and `git-annex` branches (presumably from *all* remotes unless o/w configured)
git-annex-8.20201103/doc/todo/sync_--branches__to_sync_only_specified_branches___40__e.g._git-annex__41__/comment_4_a765e998ffaecc2af681947263cd80d7._comment-13-3. push the branches from (2) back to the remotes
##############################################
git-annex-8.20201103/doc/todo/wishlist__58___disable_automatic_commits/comment_5_701ef8d7bca858150bc0ae070d21755d._comment-7- content="""
git-annex-8.20201103/doc/todo/wishlist__58___disable_automatic_commits/comment_5_701ef8d7bca858150bc0ae070d21755d._comment:8:Since I haven't learnt Haskell yet (and even if I was able to hack a patch to git-annex I'm not sure whether it would be accepted), I've hacked up [a simple `git-auto-commit` Python script for automatically committing based on a simple policy](https://github.com/aspiers/pim/blob/master/bin/git-auto-commit), together with [a shell script which invokes it every `$n` seconds](https://github.com/aspiers/pim/blob/master/bin/auto-commit-daemon).
git-annex-8.20201103/doc/todo/wishlist__58___disable_automatic_commits/comment_5_701ef8d7bca858150bc0ae070d21755d._comment-9-
##############################################
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn-22- `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment variables,
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn:23: and running `git annex enableremote $remotename embedcreds=yes`
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn-24-
##############################################
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn-30- by setting the `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID`
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn:31: environment variables, and running `git annex enableremote $remotename embedcreds=yes`
git-annex-8.20201103/doc/upgrades/insecure_embedded_creds.mdwn-32-
##############################################
git-annex-8.20201103/doc/users/candyangel.mdwn-54- * types are file, filelink, keyfile and keylink
git-annex-8.20201103/doc/users/candyangel.mdwn:55: * e.g. `git clone ${base_uri} keyfile`
git-annex-8.20201103/doc/users/candyangel.mdwn-56-* mkannex.sh is run and repository is named ${drive_serial}_${type}