Bug#245164: Should be able to get high debconf priority even if there were problems in the installation

[Kenshi Muto <kmuto@debian.org>]

Hi,

I found (maybe) same problem. After I finish base-config, debconf
goes 'medium' even if I use 'high' during 1st stage and pkgsel stage.

In my opinion, this is because base-config misses ORIG_PRIORITY when
it is called from debian-installer stage.
Here is a patch, and it looks work correctly.

------------------------------------------------------
Index: base-config
===================================================================
--- base-config	(revision 1057)
+++ base-config	(working copy)
@@ -73,14 +73,6 @@
 	trap cleanup 2
 fi
 
-ORIG_PRIORITY=$(get_priority)
-# DEBIAN_PRIORITY overrides the system priority, which would cause a
-# problem with priority chenaging, so if it's set, unset it.
-if [ ! -z "$DEBIAN_PRIORITY" ]; then
-	set_priority $DEBIAN_PRIORITY
-	unset DEBIAN_PRIORITY
-fi
-
 # Read information from first stage installer and stuff it into the debconf
 # db.
 if [ -e $DI_DB ]; then
@@ -93,6 +85,14 @@
 		--pattern='^(debconf/priority|mirror/http/proxy|mirror/suite|debian-installer/keymap|debian-installer/country|debian-installer/language)$'
 fi
 
+ORIG_PRIORITY=$(get_priority)
+# DEBIAN_PRIORITY overrides the system priority, which would cause a
+# problem with priority chenaging, so if it's set, unset it.
+if [ ! -z "$DEBIAN_PRIORITY" ]; then
+	set_priority $DEBIAN_PRIORITY
+	unset DEBIAN_PRIORITY
+fi
+
 # Copy the base-config scripts into a temp directory. This is done so if
 # base-config removes itself, it will not blow up.
 TMPDIR=/tmp/base-config.$$
------------------------------------------------------

May I commit, joeyh?

(This isn't related with Bug#228839. So we need to split again if we
apply this patch.)

Thanks,
-- 
Kenshi Muto
kmuto@debian.org