From 95e4021c09f3bfa0bacb180f5c10a702ed666ad0 Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Sun, 4 Sep 2022 13:12:55 +0000 Subject: [PATCH] --- ...inks_in_directory_remote_causes_crash.mdwn | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/bugs/Broken_symlinks_in_directory_remote_causes_crash.mdwn diff --git a/doc/bugs/Broken_symlinks_in_directory_remote_causes_crash.mdwn b/doc/bugs/Broken_symlinks_in_directory_remote_causes_crash.mdwn new file mode 100644 index 0000000000..57489b4ad5 --- /dev/null +++ b/doc/bugs/Broken_symlinks_in_directory_remote_causes_crash.mdwn @@ -0,0 +1,33 @@ +### Please describe the problem. + +I have a directory remote with importtree=yes. In that remote, I have some symlinks that are broken. (Long story; this is a file server and they work on the system that has mounted them, but are broken here.) + +### What steps will reproduce the problem? + +I've added it with `git config remote.source.annex-tracking-branch main:$REPO`. When I run `git annex sync`, I get: + +``` +commit +On branch adjusted/main(unlocked) +nothing to commit, working tree clean +ok +list source +git-annex: Unable to list contents of source: [redacted]: getFileStatus: does not exist (No such file or directory) +failed +git-annex: sync: 1 failed +``` + +### What version of git-annex are you using? On what operating system? + +8.20210223-2 on Debian + +### Please provide any additional information below. + +I would like git-annex to either: + +1. Store the symlink as a symlink, or +2. Ignore bad symlinks + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Loading in other parts of my photo collection as we speak!