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

Added a comment: indeed.

Browse source
This commit is contained in:
anarcat 2022-01-12 15:56:25 +00:00 committed by admin
parent 9104e64d3e
commit 3993421d36
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/git-annex-shell_fails_to_run_true/comment_2_5be34b5ffaee39013d24daf83a8dd437._comment Normal file
View file

@ -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!
"""]]