From 6600cd2df3aded0c4be65b1fe4aa734f4121bd66 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 22 Dec 2021 13:02:12 -0400 Subject: [PATCH] response --- ...acking_not_enabled_when_branch_is_set.mdwn | 2 ++ ..._c007c52d0a038c26e4f8fc50a2d23a18._comment | 29 +++++++++++++++++++ 2 files changed, 31 insertions(+) create mode 100644 doc/forum/export_tracking_not_enabled_when_branch_is_set/comment_1_c007c52d0a038c26e4f8fc50a2d23a18._comment diff --git a/doc/forum/export_tracking_not_enabled_when_branch_is_set.mdwn b/doc/forum/export_tracking_not_enabled_when_branch_is_set.mdwn index 98d98f7801..b31997ccd4 100644 --- a/doc/forum/export_tracking_not_enabled_when_branch_is_set.mdwn +++ b/doc/forum/export_tracking_not_enabled_when_branch_is_set.mdwn @@ -28,3 +28,5 @@ i get a result because i have it set master:devices/motoE5 this seems to be a bug, but i wanted to make sure i wasn't doing something wrong before submitting a bug report. + +[[!tag forumbug]] diff --git a/doc/forum/export_tracking_not_enabled_when_branch_is_set/comment_1_c007c52d0a038c26e4f8fc50a2d23a18._comment b/doc/forum/export_tracking_not_enabled_when_branch_is_set/comment_1_c007c52d0a038c26e4f8fc50a2d23a18._comment new file mode 100644 index 0000000000..8ec3b8f6bf --- /dev/null +++ b/doc/forum/export_tracking_not_enabled_when_branch_is_set/comment_1_c007c52d0a038c26e4f8fc50a2d23a18._comment @@ -0,0 +1,29 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-12-22T16:56:18Z" + content=""" +I think I see how this could happen. seekExportContent +checks if remoteAnnexTrackingBranch is set. If it is, +it tries to list the tree for that branch, and also gets +the export commit for that branch. If either of those actions fail, it +displays the message you saw, the same as if remoteAnnexTrackingBranch +had not been set. + +Hmm, I think the most likely reason is that master:devices/motoE5 +does not exist yet, so it fails to list the tree for it. + +If so, doing a single time `git-annex import --from moto master:devices/motoE5` +would probably make sync work. + +At least the message needs to be improved. It may also be that something +needs to be done to prevent needing to run git-annex import before sync +will work, or the documentation better document that you need to do it, +or the message suggest doing it when this happens. + +I do notice that in the [[git-annex-import]] man page, the example +does a single time `git-annex import` of the branch before setting the +git config and using sync. + +I've promoted this thread to a bug report. +"""]]