git-annex/doc/bugs/borg_not_recognizing_WORM.mdwn

### Please describe the problem.
borg special remote is apparently ignoring WORM and URL key content (probably all content without hashes?)

### What steps will reproduce the problem?
archive a repo containing WORM or URL keys with borg and sync it with git annex like in the example https://git-annex.branchable.com/special_remotes/borg/

doing `git annex list --not -i borg` later shows all WORM and URL keys not recognized being in borg

### What version of git-annex are you using? On what operating system?
git-annex version: 8.20210310
on NixOS 20.09

### 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)
Thank you for including borg, and for fixing gcrypt remotes! This is great!

> [[fixed|done]] --[[Joey]]
2021-03-24 09:44:49 +00:00			`### Please describe the problem.`
			`borg special remote is apparently ignoring WORM and URL key content (probably all content without hashes?)`

			`### What steps will reproduce the problem?`
			`archive a repo containing WORM or URL keys with borg and sync it with git annex like in the example https://git-annex.branchable.com/special_remotes/borg/`

			doing `git annex list --not -i borg` later shows all WORM and URL keys not recognized being in borg

			`### What version of git-annex are you using? On what operating system?`
			`git-annex version: 8.20210310`
			`on NixOS 20.09`

			`### 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)`
			`Thank you for including borg, and for fixing gcrypt remotes! This is great!`

borg: Support importing files that are hard linked in the borg backup Note that a key with no size field that is hard linked will result in listImportableContents reporting a file size of 0, rather than the actual size of the file. One result is that the progress meter when getting the file will seem to get stuck at 100%. Another is that the remote's preferred content expression, if it tries to match against file size, will treat it as an empty file. I don't see a way to improve the latter behavior, and the former behavior is a minor enough problem. This commit was sponsored by Jake Vosloo on Patreon. 2021-03-26 17:29:34 +00:00			`> [[fixed\|done]] --[[Joey]]`