diff --git a/doc/bugs/git_annex_doesn__39__t_cope_with_a_gcrypt__58____58__rsync__58____47____47__/comment_5_90ea78751a0402ed9fb800642cc9e128._comment b/doc/bugs/git_annex_doesn__39__t_cope_with_a_gcrypt__58____58__rsync__58____47____47__/comment_5_90ea78751a0402ed9fb800642cc9e128._comment
new file mode 100644
index 0000000000..32d7629290
--- /dev/null
+++ b/doc/bugs/git_annex_doesn__39__t_cope_with_a_gcrypt__58____58__rsync__58____47____47__/comment_5_90ea78751a0402ed9fb800642cc9e128._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2021-01-18T17:46:38Z"
+ content="""
+Oh, that format is unfortunately what git-remote-gcrypt uses:
+
+       rsync URIs
+              Note that the URI format for the rsync backend  is,  regretably,
+              non-standard.    git-remote-gcrypt  uses  rsync://user@host:path
+              whereas   plain   rsync   uses    either    user@host:path    or
+              rsync://user@host/path.
+
+Also, all git-annex commands crash due to the malformed/nonstandard url.
+Even git-annex init, or other things that don't need to access the remote at all.
+
+So this definitely needs fixing, to at least not crash on that.
+"""]]