Notice that packages requiring TTY during installations will nowadays fail to install in debian-installer (see #282147), buildd chroots, and will hang piuparts testing.
Therefor packages using tty in maintainer scripts are already de facto buggy in common debian usage situations. The TTY requirement for debian hinders package managment GUI development and makes automated installation of debian to clusters and classrooms unnecessarily hard. Checking from piuparts-hangers list[1], there is 5 packages left (blootbot, emacspeak, runit-run, slash, tcpquota) that prompt without debconf by default. There is probably a dozen or so packages that prompt only under special circumstances. [1] http://svn.debian.org/wsvn/collab-qa/debcluster/scripts/piuparts/piuparts.untestable?op=file&rev=0&sc=0 -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
