borg: Fix a bug that prevented importing keys of type URL and WORM
Keys stored on the filesystem are mangled by keyFile to avoid problem chars. So, that mangling has to be reversed when parsing files from a borg backup back to a key. The directory special remote also so mangles them. Some other special remotes do not; eg S3 just serializes the key -- but S3 object names are not limited to filesystem valid filenames anyway, so a S3 server must not map them directly to files in any case. It seems unlikely that a borg backup of some such special remote will get broken by this change. This commit was sponsored by Graham Spencer on Patreon.
This commit is contained in:
parent
537f9d9a11
commit
31eb5fddf3
5 changed files with 13 additions and 3 deletions
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 3"""
|
||||
date="2021-03-26T16:05:49Z"
|
||||
content="""
|
||||
I've fixed this bug. Note that, git-annex won't re-scan borg archives that
|
||||
it's already scanned, so you will need to make a new borg backup in order
|
||||
to add a new archive, and then git-annex will notice the files it missed
|
||||
before.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue