| Summary: | No indication that destination must exist for backup to proceed | ||
|---|---|---|---|
| Product: | [Applications] kup | Reporter: | Kai Uwe Broulik <kde> |
| Component: | general | Assignee: | Simon Persson <simon.persson> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | public |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Kai Uwe Broulik
2022-08-26 07:09:43 UTC
Thanks for reporting! It was indeed created with mounted folders in mind, so a destination folder not existing would be normal at most times. But like you say, the configuration module might be good time to insist that it should exist. It could offer to create the folder, maybe in a warning message. This looks like a relative to https://bugs.kde.org/show_bug.cgi?id=453919 Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 445391 M +50 -1 kcm/backupplanwidget.cpp M +3 -0 kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 |