I can confirm this problem when using the Readline debconf frontend
without libterm-readline-gnu-perl installed.  In this situation, no
default values are displayed, and hitting enter sets a blank value in
the debconf database. Teodor ran into this problem because $TERM was not
set in his environment, so debconf fell back to a Readline interface.

I should at this point note that when testing this problem with schroot,
developers should be careful that their home directories are not bind
mounted within the chroot. :(

The consequences are severe, so I propose this patch:

--- a/debian/dak.postinst       2009-02-15 01:44:40.000000000 +0000
+++ b/debian/dak.postinst       2009-02-15 01:55:58.000000000 +0000
@@ -23,6 +23,12 @@
 
                db_get "dak/path"
                path="$RET"
+
+               # Some debconf interfaces use empty defaults.
+               if [ "$path" == "" ]; then
+                       path="/opt/dak"
+               fi
+
                db_get "dak/hostname"
                hostn="$RET"
                db_get "dak/archivename"


-- 
Tim Retout <t...@retout.co.uk>




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to