c633144d28
The subtle part of this is what happens when the remote fails to remove an empty directory. The removal from the export needs to fail in that case, so the removal will be tried again later. However, removeExportLocation has already been run and changed the export db, so if the next run checks getExportLocation, it might decide nothing remains to be done, leaving the empty directory. Dealt with that by making removeEmptyDirectories, handle a failure by calling addExportLocation, reverting the database changes so the next run will be guaranteed to try deleting the empty directory again. This commit was sponsored by Thomas Hochstein on Patreon. |
||
|---|---|---|
| .. | ||
| Keys | ||
| Export.hs | ||
| Fsck.hs | ||
| Handle.hs | ||
| Init.hs | ||
| Keys.hs | ||
| Queue.hs | ||
| Types.hs | ||