close 1:5.0.3-1
thanks

Hi,

On Thu, Jan 28, 2016 at 01:42:25PM +0100, Thomas Liljenstam wrote:
>    This bug is closed, I have verified that the issue is gone in 5.0.3.2.
>    Unfortunately I don’t know when it was fixed.

let's mark it as fixed in 1:5.0.3-1 then...

Regards,

Rene

Reply via email to