Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
b2f3928971
4 changed files with 35 additions and 0 deletions
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="mih"
|
||||
avatar="http://cdn.libravatar.org/avatar/f881df265a423e4f24eff27c623148fd"
|
||||
subject="Thanks!"
|
||||
date="2022-01-11T18:59:36Z"
|
||||
content="""
|
||||
That was the missing piece for me. Thank you!
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="yarikoptic"
|
||||
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
|
||||
subject="comment 3"
|
||||
date="2022-01-12T19:33:15Z"
|
||||
content="""
|
||||
Still checking but so far looks good with `8.20211231+git69-ga55fc567c-1~ndall+1` -- thank you!
|
||||
"""]]
|
|
@ -162,3 +162,5 @@ Key part above:
|
|||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||
|
||||
I'm a long time git-annex user (early adopter, even?) and git-annex is generally serving my uses very well, both as a backup and archival system. The encryption features, however, are a bit more obscure than my tolerance level right now. Thankfully, there is the [[special_remotes/borg/]] I'm thinking of using to replace all this complexity in the future...
|
||||
|
||||
-- [[done]], problem was with a configuration in the gcrypt remote sandbox. -- [[anarcat]]
|
||||
|
|
|
@ -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!
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue