Hi, Just out of curiosity, I tested this bug in a sid VM today and reproduced the failure with 4.0.4-1. Noting that 4.0.5 was available upstream, I used uscan and uupdate to update to 4.0.5 and re-tested in the same VM. The build fails in a similar way.
From a quick comparison of the build logs, it does look like the same failure. Hope that helps. -- Neil Williams ============= [email protected] https://www.codehelp.co.uk/
