Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2021-04-14 16:20:13 -04:00
commit 17646b0b31
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 27 additions and 0 deletions

View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="jbwexler@f0760d2c023f7660c38fb17889d4cd6930183696"
nickname="jbwexler"
avatar="http://cdn.libravatar.org/avatar/843be3c6c30b8867c2a0c6ddfb5ad45b"
subject="thanks"
date="2021-04-14T19:03:09Z"
content="""
Thanks for the quick response. Do you see any other way to solve this error? I'm currently stuck as to how to create this special remote.
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="Lukey"
avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b"
subject="comment 3"
date="2021-04-14T20:06:29Z"
content="""
I guess you could put your self-signed certificate in your ca-store (usually `/etc/ssl/certs`), so the tls library accepts it as a valid certificate. This is much safer than disabling certificate validation altogether.
"""]]

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment to joey response on cp --reflink workaround"
date="2021-04-14T18:04:49Z"
content="""
> Of course, if you can get the content into the git-annex repository by other means like manual cp --reflink, git-annex will never have any reason to transfer the imported file from the remote, so that workaround would work.
FWIW: doing that now. Minor pain will come later when I will need to update it (only once again) with a new sync'ed data (some files will be added, some removed) -- to simplify my own life I will just `rm -rf` in target git-annex repo, redo `cp --reflink` and redo `datalad save` (which will take care about removing gone, and `git-annex add` on all others -- but that would take again many hours to complete even though only a handful of files will be changed)
"""]]