mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
git-annex/doc/bugs/sync_with_clone_protocol_error.mdwn

16 lines
580 B
Text
Raw Normal View History

bug report
2017-03-17 04:22:19 +00:00
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]]
git-annex-shell: run all commands with noMessages Fix bug when used with a recently cloned repository, where "merging" messages were included in the output of configlist (and perhaps other commands) and caused a "Failed to get annex.uuid configuration" error. This does not seem to have been a reversion. I saw this with configlist, but it seems possible for other commands to be effected, and it might not always happen only after a fresh clone. Eg, if a foo/git-annex branch is pushed to the remote, the next git-annex-shell will auto-merge it and display the message. Decided to run all git-annex-shell commands with noMessages, even ones that don't currently use stdout for structured communication. Better to keep open the possibility for using stdout in the future. This commit was supported by the NSF-funded DataLad project
2017-03-17 16:28:08 +00:00
> [[fixed|done]] --[[Joey]]
Reference in a new issue Copy permalink