Found it. /lib/debian-installer.d/S25env2debconf runs env2debconf from rootskel, which already tries to load the frontend module (i.e., check DEBIAN_FRONTEND, fallback to /etc/cdebconf.conf defaults (newt), export DEBIAN_FRONTEND). So when S50frontend is run, it falls through as a no-op since that script checks for -z $DEBIAN_FRONTEND.
One way to fix this would be to rename S50frontend such that it runs before S25env2debconf. However, this smells fishy since IMO S25env2debconf shouldn't try to load the frontend module in the first place, should it? Comments? -- CYa, Mario | Debian Developer <URL:http://debian.org/> | Get my public key via finger [EMAIL PROTECTED] | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
pgpKpGRXVXxJV.pgp
Description: PGP signature
