diff options
authorJoey Hess2018-04-30 16:23:14 -0400
committerJoey Hess2018-04-30 16:23:14 -0400
commita8fa6e5f63b466d97a04fb9e78e05b417aa3a33c (patch)
parentfbe9e7ff6bd6c1feba0f04fe07cb7b086ec38376 (diff)
notes on failed attempt to migrate
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/todo/depend_on_concurrent-output.mdwn b/doc/todo/depend_on_concurrent-output.mdwn
index 347ea9e5..c3641385 100644
--- a/doc/todo/depend_on_concurrent-output.mdwn
+++ b/doc/todo/depend_on_concurrent-output.mdwn
@@ -7,3 +7,23 @@ Waiting on concurrent-output reaching Debian stable.
> supporting the current oldstable, I believe.. --[[Joey]]
[[!tag user/joey]]
+> This was attempted again in 2018 and had to be reverted
+> in [[!commit b6ac64737b59e74d4aa2d889690e8fab3772d2c6]].
+> The strange output I was seeing is the first line
+> of "apt-cache policy apache2" (but not subsequent lines)
+> and the ssh-keygen command run by `genSSHFP'`
+> Propellor also misbehaved in some other ways likely due to not seeing
+> the command output it expected. In particular Git.cloned must have
+> failed to see an origin url in git config output, because it nuked and
+> re-cloned a git repo (losing data).
+> So, it seems that readProcess was somehow leaking output to the console
+> and also likely not providing it to the caller.
+> The affected system had libghc-concurrent-output-dev 1.10.5-1 installed
+> from debian. That is a somewhat old version and perhaps it was buggy?
+> However, I have not had any luck reproducing the problem there running
+> readProcess in ghci. --[[Joey]]