diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-03-17 00:22:19 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-03-17 00:22:19 -0400 |
| commit | 2e22df59273ddb39ea8f5545e8ac4830a4a31b7c (patch) | |
| tree | 9e53ac8f24a15a892b8b0e1a354562ace12490f9 | |
| parent | d995c27794b7d8a492e543cd1e270a30bf3f15bf (diff) | |
bug report
| -rw-r--r-- | doc/bugs/sync_with_clone_protocol_error.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/sync_with_clone_protocol_error.mdwn b/doc/bugs/sync_with_clone_protocol_error.mdwn new file mode 100644 index 000000000..47b61483c --- /dev/null +++ b/doc/bugs/sync_with_clone_protocol_error.mdwn @@ -0,0 +1,13 @@ + Failed to get annex.uuid configuration of repository clam + + Instead, got: "(merging origin/git-annex origin/synced/git-annex into git-annex...)\n(recording state in git...)\nannex.uuid=$obscured\ncore.gcrypt-id=\n" + +Seen after cloning the repository to clam, not running git-annex init +in it, adding clam as a remote, and git annex sync clam. +Apparently git-annex-shell outputs some merging messages in this +case, which breaks the protocol. + +Next git-annex sync clam worked ok and got the UUID. + +clam has git-annex 6.20170101 installed. +--[[Joey]] |