summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorJoey Hess2020-06-10 16:13:10 -0400
committerJoey Hess2020-06-10 16:13:10 -0400
commite6d4139e15b3a52f4a60178bb7d15ba96f191340 (patch)
tree1f479171aa9fb3afbfb37c907495de2107c77dc0 /doc/todo
parentad2c6ae1f904b5d94e227944c96db657410934ee (diff)
more
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/depend_on_concurrent-output.mdwn8
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/todo/depend_on_concurrent-output.mdwn b/doc/todo/depend_on_concurrent-output.mdwn
index 2503fe2e..5826506e 100644
--- a/doc/todo/depend_on_concurrent-output.mdwn
+++ b/doc/todo/depend_on_concurrent-output.mdwn
@@ -35,8 +35,10 @@ Waiting on concurrent-output reaching Debian stable.
> > 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.
+> > a STM transaction deadlock. Seemed to only happen when spinning the
+> > host remotely, or not always; I tried to reproduce it running propellor
+> > manually to bisect concurrent-output but without success.
> >
> > This is really looking like a reversion, or several, in newer
-> > versions of concurrent-output. --[[Joey]]
+> > versions of concurrent-output. The code bundled with propellor is
+> > the same as concurrent-output 1.7.4.