summaryrefslogtreecommitdiff
path: root/bugs/symlink-as-backup-root.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'bugs/symlink-as-backup-root.mdwn')
-rw-r--r--bugs/symlink-as-backup-root.mdwn24
1 files changed, 0 insertions, 24 deletions
diff --git a/bugs/symlink-as-backup-root.mdwn b/bugs/symlink-as-backup-root.mdwn
deleted file mode 100644
index d5b4f29..0000000
--- a/bugs/symlink-as-backup-root.mdwn
+++ /dev/null
@@ -1,24 +0,0 @@
-From Lars Kruse:
-
-> Thus the situation seems to be that obnam stores all relevant chunks,
-> but due to the symlink pointing to something outside of the repository
-> I cannot restore
-
-From liw: This is obviously a bug. Obnam should either give an error
-if the backup root is a symlink, or back it up as a symlink, not
-recurse into the directory and then backup that and only then ruin
-everything by backing up the symlink as a symlink.
-
----
-
-This should now be fixed to give an error message when you backup.
-I can't currently give access to the hidden files easily, I'm afraid,
-but if you change your backup root to be the directory pointed at by
-the symlink, and run a backup, it should go fairly fast and give you
-access to your files.
-
-Later, I may consider allowing the root to be a symlink to a
-directory, but that'll require bigger changes than this error message,
-I'm afraid. Patches to implement this would be welcome.
-
-[[done]] --liw