From 3993421d36e05daef5337d531465b080aae3b645 Mon Sep 17 00:00:00 2001 From: anarcat Date: Wed, 12 Jan 2022 15:56:25 +0000 Subject: [PATCH] Added a comment: indeed. --- ..._2_5be34b5ffaee39013d24daf83a8dd437._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/git-annex-shell_fails_to_run_true/comment_2_5be34b5ffaee39013d24daf83a8dd437._comment diff --git a/doc/bugs/git-annex-shell_fails_to_run_true/comment_2_5be34b5ffaee39013d24daf83a8dd437._comment b/doc/bugs/git-annex-shell_fails_to_run_true/comment_2_5be34b5ffaee39013d24daf83a8dd437._comment new file mode 100644 index 0000000000..a9d422e054 --- /dev/null +++ b/doc/bugs/git-annex-shell_fails_to_run_true/comment_2_5be34b5ffaee39013d24daf83a8dd437._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="indeed." + date="2022-01-12T15:56:25Z" + content=""" +the problem was that i had a `~/git-shell-commands/rsync` overriding the rsync command to try to restrict *that*, since i'm using a gcrypt remote... it was clunky and badly designed and, ultimately, insecure. i replaced it with `rrsync /home/anarcat/offsite/` but even that is not the best either, as the script says it \"assumes someone will not subvert the rsync protocol\" which hardly seems reassuring. + +i also had to change my remotes to follow the \"chroot\" of sorts: + + git config remote.offsite-annex.annex-rsyncurl anarcat@remote-annex:Videos.annex/ + git remote set-url offsite-git gcrypt::rsync://anarcat@remote-annex:Videos.git/ + +Running `git fetch` by hand convinced me the problem wasn't git-annex related... From there I reread the git-annex-shell and git-shell commands and noticed that bit about the obscure `git-shell-commands` directory, and found that jem. I even had an error in `journalctl -f` that confirm the problem, something i overlooked as well... + +so this indeed seems like a problem on my end. sorry for the delay and the noise! +"""]]