This commit is contained in:
Joey Hess 2021-12-22 13:02:12 -04:00
parent 139683a56d
commit 6600cd2df3
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 31 additions and 0 deletions

View file

@ -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]]

View file

@ -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.
"""]]