Package: cdebconf Version: 0.66 Severity: important Tags: d-i hw-detect does the following: INPUT medium hw-detect/start_pcmcia GO FSET hw-detect/start_pcmcia seen true hw-detect/start_pcmcia is a boolean, with a default value of true. Due to priority, the input defaults to not showing the question, so the value is still inherited from the template. After the fset, cdebconf incorrectly makes the stanza for this question in config.dat have an empty value, like this: Name: hw-detect/start_pcmcia Template: hw-detect/start_pcmcia Value: Owners: d-i Flags: seen This plays havoc with stuff that expects to get a true/false from a boolean. In this particular example, it utterly breaks pcmcia restarting in d-i. It's out of spec for a boolean to have a value that is not true or false. The correct thing to do in this case is to either copy the Value from the template, or not put in a Value field when the value is not set, and inherit from the template still. debconf does the latter, which cdebconf should do depends on its internal design, I suppose. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.26 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages libdebconfclient0-dev depends on: ii libc6-dev 2.3.2.ds1-13 GNU C Library: Development Librari ii libdebconfclient0 0.66 Debian Configuration Management Sy -- no debconf information -- see shy jo
Attachment:
signature.asc
Description: Digital signature