Bug#206684: debian-policy: Proposal for going ahead with mandatory debconf use for prompting
Lucas Nussbaum <lucas@lucas-nussbaum.net> writes:
> On 08/03/07 at 08:02 +0100, Lucas Nussbaum wrote:
>> Well, that's really the worst case scenario. I would have to run
>> piuparts again to get better numbers, since:
>>
>> - I'm running piuparts on etch, not sid, and packages
>> in-sid-but-not-in-etch are likely to be less well maintained, so
>> changes are higher that they do bad stuff with /dev/tty
>>
>> - I use a workaround (make /dev/tty a copy of /dev/null) so that most
>> packages reading /dev/tty don't block during the test
>>
>> I'll try to give a better estimation soon.
> Indeed, there are probably less packages to fix that I thought.
> Christian, would you be interested in pushing a lenny release goal about
> this?
If the release team approves, I would be happy to change the should in
Policy to must. Do we need to make any exceptions for essential packages
like libc6 that may be configured before debconf is available for some
reason?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: