On 02/09/2018 at 14:18 Ludovic Courtès writes: > For now I’ve pushed a workaround in > a68fdfea96370c8a4b95af1fcd6e2fd7eb72da29, which basically downgrades to > 0.10 until upstream comes up with a fix.
OK, I knew it needed to go upstream but I also thought it must have worked at some point. Thank you for the workaround ;-) - George
