diff --git a/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_24_1c96a68c27ba09cd1f8c035dd026582b._comment b/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_24_1c96a68c27ba09cd1f8c035dd026582b._comment
new file mode 100644
index 0000000000..66406692bc
--- /dev/null
+++ b/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_24_1c96a68c27ba09cd1f8c035dd026582b._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 24"
+ date="2018-11-05T20:53:48Z"
+ content="""
+Great to hear that bottom issue is revealed!
+
+FWIW regarding
+
+> If you wait 300 seconds, it should give up waiting for the pid lock, and complain about it to stderr, which may or may not be visible across the ssh connection.
+
+waited for ~50 minutes, `git annex get` process is still hanging without any additional output provided
+"""]]
diff --git a/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_25_d107200df348bc2b97e2fefc4342e49a._comment b/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_25_d107200df348bc2b97e2fefc4342e49a._comment
new file mode 100644
index 0000000000..08dcaed633
--- /dev/null
+++ b/doc/bugs/annex_get_-J_16_via_ssh_stalls_/comment_25_d107200df348bc2b97e2fefc4342e49a._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 25"
+ date="2018-11-05T21:01:35Z"
+ content="""
+Re
+
+> I've seen the test fail that way, where apparently all gets from the remote repo are failing, on the autobuilders once or twice, but not reproducably...
+
+Unfortunately this time I was not as fortunate to reliably reproduce it (yet) :-(  for me I believe it happened for the first time ever although I could be wrong.
+How do you know which test(s) fail and how to restart only a failing test (e.g. by name?) -- I find it difficult to parse logged output to figure out test names/boundaries since intermixed with git output etc which also includes error messages on conflicts etc.
+"""]]
diff --git a/doc/todo/git-annex_7.20181105_not_buildable_against_Debian_stretch.mdwn b/doc/todo/git-annex_7.20181105_not_buildable_against_Debian_stretch.mdwn
new file mode 100644
index 0000000000..66aed0d48e
--- /dev/null
+++ b/doc/todo/git-annex_7.20181105_not_buildable_against_Debian_stretch.mdwn
@@ -0,0 +1,10 @@
+    [249 of 596] Compiling Database.Init    ( Database/Init.hs, dist/build/git-annex/git-annex-tmp/Database/Init.o )
+    
+    Database/Init.hs:52:27: error:
+        Not in scope: type constructor or class ‘SqliteConnectionInfo’
+    Makefile:32: recipe for target 'git-annex' failed
+    make[1]: *** [git-annex] Error 1
+
+Backporting recent persistent-sqlite to stretch is highly unlikely to succeed, given how tangled Haskell library dependencies tend to be.  So, unless there is an easy fix for this, git-annex will have to be removed from stretch-backports.  That would be a shame, but I guess buster isn't so far away now!
+
+--spwhitton