On 22/07/17 10:08, Adrian Bunk wrote: > This was fixed in 3.1-3, but the bug is back in 3.1-5 Sorry about that - a bit of confusion with two people working on the package at the same time.