comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 15 Aug 2023 17:21:28 +0000 (13:21 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 15 Aug 2023 17:21:28 +0000 (13:21 -0400)
doc/bugs/Sync_fails_when_borg_remote_is_inaccessible/comment_1_5e83630a60aa0242969bd1279a70628a._comment [new file with mode: 0644]

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 (file)
index 0000000..70684e3
--- /dev/null
@@ -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.
+"""]]