Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No warning is issued when directory is modified and no longer exists when attempting to backup files on shutdown #24

Closed
monasar opened this issue Jan 29, 2015 · 0 comments
Assignees
Labels
Milestone

Comments

@monasar
Copy link

monasar commented Jan 29, 2015

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:
  1. Go to Options -> Edit preferences -> Miscellaneous tab
  2. In the Backup Folder, browse and create a new folder as a directory.
    • create a folder called 'test', and save.
  3. For the On Shutdown option: Select Backup to file
  4. Delete or rename the directory you just created.
    • delete or rename 'test'
  5. Close BORG Calendar. The backup files will not be stored and no notification of the directory not existing will be issued
  6. 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.
@mikeberger mikeberger added the bug label Jan 30, 2015
@mikeberger mikeberger added this to the 1.8.2 milestone Jan 30, 2015
@mikeberger mikeberger self-assigned this Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants