borgmatic fails if /etc/borgmatic/exclude does not exist #4
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#4
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?
atticmatic/borgmatic should allow for cases where the "exclude" file does not exist. Maybe I don't want to create an exclude file at the start. Right now, it errors out if that file was not created during setup.
Imported from Taiga issue 3 (done). Created on 2015-07-26T14:09:02+0000 by Thomas Harold.
Great point.
Comment on 2015-07-26T15:09:24+0000 by Dan Helfman.
This has been fixed in atticmatic 0.1.2, just released. The fix was to silently accept a missing excludes file if no excludes filename was specified on the command-line.
Comment on 2015-07-27T04:06:12+0000 by Dan Helfman.