Bug#228839: debconf: Could you change default priority to 'high'?

[Christian Perrier <bubulle@debian.org>]

Quoting Kenshi Muto (kmuto@debian.org):
> Package: debconf
> Version: 1.4.29
> Severity: wishlist
> 
> I'm sorry for bring up again about priority issue.
> This wishlist is similar with #228839, but JoeyH looks don't
> want to provide priority question in base-config.

I think we could have a quite uninvasive workaround to the priority
changes problem:

1) record the *initial* priority just before starting first stage (the
priority is either the default...or the one we had by setting
DEBCONF_PRIORITY at boot prompt). This could be in debconf/initial-priority

2)run 1st stage with possible priority lowered because of "Go back" or
errors

3)restore the initial priority at the end of 1st stage by copying the
value of debconf/initial-priority back to debconf/priority

4)then 2nd will start at the same priority than 1st

5)at the end of 2nd stage, restore the priority to the initial
priority again....and finally run "dpkg-reconfigure debconf" is the
value is lower than "high".

This will guarantee that the priority is always "high" at the end of
the installation whatever happens during the install....and thus, the
vast majority of users will use the recommended default.

This may also require to change the default for debconf to "high".