TW
This is now in borg2 branch, so the `csize` related issues are solved by removing it everywhere. Update: merged into master now.
Note: size, csize, ctype, clevel is now available as separate encrypted metadata via `repo.get(id, read_data=False)` and `RepoObj.parse_meta(chunk)`.
Guess the easiest explanation is that the repo path is incorrect. Considering it is a relative path (see missing `/` at the left), it depends on the current working directory...
does `borg delete [--force [--force]]` work on such a repo?
OK, so while there is some sub-optimal borg behaviour for the remote repo case, there is at least some easy way to clean up again.
@mconigliaro if you can reproduce this with an up-to-date borg (like 1.1.10 or master branch, if you prefer), please open a separate issue for that.
maybe related: #6912
@palao did you see my feedback? you can just continue within this pull request, just do some fixup commits. also, considering age of this PR, maybe updating your local master...
Considering this PR is a bit older already, maybe you could: - update your local master branch - switch to your PR branch - `git rebase -i master` # ......
@derekkaup what did you want to tell us here?