diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-05-19 18:25:59 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-05-19 18:25:59 -0400 |
| commit | 45799530677d9b53dbcd50f943e28c85019929d0 (patch) | |
| tree | 07c6883dc4b02629ae91fdfd9120007060463b0e | |
| parent | 7cef0ecb57c420a8b7b145f542320c7ab635f2ed (diff) | |
fixed gcrypt OSX bug
| -rw-r--r-- | doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn index d45dcdc9c..41122f8a6 100644 --- a/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn +++ b/doc/bugs/remote_gcrypt_based_repos_and_conflicting_uuids.mdwn @@ -21,3 +21,10 @@ It all seems to work well until I try to do any kind git annex operation from th # End of transcript or log. """]] + +> [[fixed|done]]; <>. I have updated the OSX autobuilder so tonight's +> build will include the fixed git-remote-gcrypt. --[[Joey]] +> +> Note that gcrypt repositories affected by this bug are in fact empty, so +> the first time a push is made with the fixed gcrypt it will probably +> generate a new gcrypt-id and push everything. |