Restore actions cannot find the repository when its path is relative #691
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#691
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I'm trying to restore a database dump as part of manual testing a separate feature.
Steps to reproduce
test.yaml
) with a repository that has a relative path, say in the current directory. Also configure a database in the configuration file.borgmatic create -c test.yaml
to create an archive containing a database dump.borgmatic -c test.yaml -v 2 restore --archive latest
to attempt to restore that dump.Actual behavior
Expected behavior
Successful database restore.
Other notes / implementation ideas
This bug does not manifest when the repository path is absolute. That's likely because the working directory change in
borgmatic/borg/extract.py
only causes issues when the repository path is relative.Environment
borgmatic version: main
borgmatic installation method:
pip install --editable
Borg version: 1.2.4
Python version: 3.10.10
Database version: PostgreSQL 14.3
operating system and version: Manjaro Linux stable
Fixed in main.
This was just released in borgmatic 1.7.13!