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

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

Browse source
This commit is contained in:
Joey Hess 2021-04-05 15:32:08 -04:00
commit 98b223a71c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/Cannot_delete_remote_when_ssh_sync_fails/comment_3_35a08daa2776c648d5ee010b77e72bd4._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="https://launchpad.net/~r0lf"
nickname="r0lf"
avatar="http://cdn.libravatar.org/avatar/aa82122557e706df7ba83bd1983eb79ef1ba2e51350217850176d4f9a1bb2bc0"
subject="still an issue in Ubuntu Focal"
date="2021-04-05T01:28:46Z"
content="""
This is still an issue in Ubuntu Focal which has version 8.20200226-1 of git-annex.
What I did here is to create a gcrypt remote on hidrive.strato.com over plain git. The obfuscated URL is url = \"gcrypt::git.hidrive.strato.com:users/myuser/gcrypt.git#gcrypt\". That remote shows as \"syncing enabled (metadata only)\" in the webapp interface and cannot be deleted there. I don't think strato.com has git-annex-shell installed.
"""]]

7
doc/forum/How_to_fix__58_____40__transfer_already_in_progress__44___or_....mdwn Normal file
View file

@ -0,0 +1,7 @@
This is more of a mini-tip or self-answered question: What to do when git-annex says "... (transfer already in progress, or unable to take transfer lock)" when trying to transfer a file to a special remote.
If you are sure that there are no other git-annex processes trying to upload (i.e. you cancelled it but git-annex crashed in the middle or something), have a look at `.git/annex/transfer/upload/`. This is only for when you can't get them to be copied by re-running the git-annex command, only for when subsequent calls don't fix it. Intermittent issues might be caused by multiple jobs, so dropping the `--jobs` parameter should fix those.
In my case I had two keys that git-annex refused to copy to a special remote no matter what I did and those dirs contained files named after the keys + ones with `lck.` prefix. After removing those dirs, the upload went through as expected.
Hope this helps someone :)

8
doc/todo/whishlist__58___GPG_alternatives_like_AGE.mdwn Normal file
View file

@ -0,0 +1,8 @@
GA uses GPG for encryption but it's neither fast, user friendly or particularly secure (C software from the 90s with huge legacy debt...).
It'd be really nice if you could use a faster, simpler/leaner, modern and reasonably secure piece of software instead for encryption in GA.
I'm not too deep into this but https://github.com/FiloSottile/age looks like an ideal replacement for what GA currently needs GPG for:
It's fast (encrypts `/dev/zero` at 1.4GiB/s on my machine), modern, simple and designed to integrate well with other tools via the command line. Its creator is the Golang security lead, so the crypto is probably good too ;)
Age seems to be closing in on its "production-ready" 1.0.0 release, so it might be worth having a look at now.