You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the backup directory is modified e.g moving it to another location, renaming, or even deleting it, the BORG Calendar will not store the backup files provided that the user selected the backup option on shutdown. The user will be misled to believe that the BORG Calendar is actually creating backup files since no warning is given that the directory is missing.
Go to Options -> Edit preferences -> Miscellaneous tab
In the Backup Folder, browse and create a new folder as a directory.
create a folder called 'test', and save.
For the On Shutdown option: Select Backup to file
Delete or rename the directory you just created.
delete or rename 'test'
Close BORG Calendar. The backup files will not be stored and no notification of the directory not existing will be issued
Same behavior applies when selecting 'On Shutdown: Prompt for backup action'
Suggestion for Fix:
If the directory selected in Backup Folder option was modified/no longer exists, create the directory and store the backup files there.
Another solution, If the directory selected in Backup Folder option was modified/no longer exists, notify the user that the directory does not exist and hence no backup of the files are being stored.
The text was updated successfully, but these errors were encountered:
Problem description:
When the backup directory is modified e.g moving it to another location, renaming, or even deleting it, the BORG Calendar will not store the backup files provided that the user selected the backup option on shutdown. The user will be misled to believe that the BORG Calendar is actually creating backup files since no warning is given that the directory is missing.
Environment and Setup:
Hardware: Clevo Laptop, Desktop
OS: ArchLinux Kernal v.3.18.3, Windows 7
BORGCalendar Version: 1.8.1
How to reproduce:
Suggestion for Fix:
The text was updated successfully, but these errors were encountered: