[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#206684: debian-policy: Proposal for going ahead with mandatory debconf use for prompting



On 08/03/07 at 08:02 +0100, Lucas Nussbaum wrote:
> On 07/03/07 at 23:07 +0100, Christian Perrier wrote:
> > > I would really like to see that happening at the beginning of the lenny
> > > release cycle. Packages that prompt without using debconf make it
> > > unnecessary difficult to test them using piuparts.
> > > 
> > > Looking at my piuparts results (testing packages in etch), most packages
> > > that prompt the user already do that through debconf, so it would not
> > > result in more than 50 or 100 bugs (and that's the worst case scenario).
> > 
> > Hmmm, that many?
> > 
> > [..]
> > 
> > I'm still puzzled by the number of package you announce, Lucas.
> 
> 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?
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Attachment: signature.asc
Description: Digital signature


Reply to: