From 9fffa85a9e69b1f04fd017d7f7bb0737ab153c2e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 15 Aug 2023 13:21:28 -0400 Subject: [PATCH] comment --- ..._1_5e83630a60aa0242969bd1279a70628a._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/Sync_fails_when_borg_remote_is_inaccessible/comment_1_5e83630a60aa0242969bd1279a70628a._comment diff --git a/doc/bugs/Sync_fails_when_borg_remote_is_inaccessible/comment_1_5e83630a60aa0242969bd1279a70628a._comment b/doc/bugs/Sync_fails_when_borg_remote_is_inaccessible/comment_1_5e83630a60aa0242969bd1279a70628a._comment new file mode 100644 index 0000000000..70684e3064 --- /dev/null +++ b/doc/bugs/Sync_fails_when_borg_remote_is_inaccessible/comment_1_5e83630a60aa0242969bd1279a70628a._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2023-08-15T16:59:11Z" + content=""" +Note that same thing happens when a directory special remote is configured +with importtree=yes exporttree=yes and the directory gets moved out of the +way. (Well, it does now.. Previously it failed to fail and imported an empty +tree, which was much worse a bug.) + +Failure to access the borg repo doesn't prevent the rest of the sync from +happening though. It still syncs with other remotes. + +Yes, there is a special case in sync to skip local git repositories that +are not present. Skipping borg and directory special remotes would need +that special case to be improved to an interface. +"""]]