Mattia Dongili wrote:
that's exactely my problem. I know debconf must be used as less as possible, but if I can't autoconfigure the daemon and thus abort its startup/execution, I have to tell something to the user and try to exit the installation process cleanly (asking for some action to take and to run `dpkg-reconfigure cpufreqd` later). which priority could my warning be?
If something is going to break, there is a reason to have a medium or high priority warning. I am glad to see you're only going to do it in cases where automatic configuration has failed; that, in my opinion, is the correct way to use debconf warnings.