Comment 4 for bug 63721

This turns out to be a bug in the confirm_changes function in partman-base; I dropped the priority of the partman*/confirm_nochanges questions to medium way back in the hoary cycle for reasons I no longer recall. These reasons are almost certainly obsolete nowadays anyway, so I'll revert that change.