From ad2c6ae1f904b5d94e227944c96db657410934ee Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 10 Jun 2020 15:19:02 -0400 Subject: meh --- doc/todo/depend_on_concurrent-output.mdwn | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc/todo') diff --git a/doc/todo/depend_on_concurrent-output.mdwn b/doc/todo/depend_on_concurrent-output.mdwn index c3641385..2503fe2e 100644 --- a/doc/todo/depend_on_concurrent-output.mdwn +++ b/doc/todo/depend_on_concurrent-output.mdwn @@ -27,3 +27,16 @@ Waiting on concurrent-output reaching Debian stable. > 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]] +> +> > Tried again in 2020, same bugs still happened. On a system running +> > debian unstable with concurrent-output 1.10.9, and a system running stable that +> > had cabal installed concurrent-output 1.10.11. +> > +> > The former system (kite) had the strange output problem. +> > +> > The latter system (keysafe) seemed ok but crashed at the end with +> > a STM transaction deadlock. Downgrading to concurrent-output 1.10.6 +> > eliminated that problem. +> > +> > This is really looking like a reversion, or several, in newer +> > versions of concurrent-output. --[[Joey]] -- cgit v1.2.3