Comment 16 for bug 1523194

Trust me, I have identified the whole of the problem after enabling full trace of the relevant scripts and going through the logs with a fine tooth comb. The bug is not *in* Ubiquity therefore it is incorrect to leave it tasked there. The Ubiquity developers do not need to know about it as they can not fix it. It also would still say there is a problem in ubiquity after it is fixed in partman-crypto. Unfortunately launchpad does not have the capability to record that a bug affects another package without actually being in that package and needing to be fixed in that package.