Fix retrieval of content from borg repos accessed over ssh
It was making the borgrepo path absolute.. even when it was a ssh repository. Made BorgRepo a newtype, to guard against accidentially treating it like a FilePath. Sponsored-by: Graham Spencer on Patreon
This commit is contained in:
parent
b2a7a665b2
commit
c952c485c8
4 changed files with 42 additions and 12 deletions
|
@ -71,3 +71,5 @@ NOTE: I tried several variations of the ssh url syntax, but they all resulted in
|
|||
### 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)
|
||||
|
||||
Definitely. I love git-annex. I LOVE it. It has no equal and is the secret to my productivity, not to mention peace of mind in this epoch. Much, much respect.
|
||||
|
||||
> [[fixed|done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,15 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2021-07-15T16:20:33Z"
|
||||
content="""
|
||||
Thanks for a good repo recipe. I only needed to add a "borg init
|
||||
$BORG_REPO -e none" to see the bug.
|
||||
|
||||
The bug is because it had to make the path to the borg repo absolute,
|
||||
since it's running borg inside a temp directory. And the case of a ssh
|
||||
location was not considered when doing that.
|
||||
|
||||
Fixed and cleaned up the BorgRepo data type to avoid this kind of dumb
|
||||
mistake in the future. ;-)
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue