Dave Sherohman wrote: > Whenever I install a new system, debconf (or rather, the minimal version on > the install disks) throws up a curses-based menu asking what mode I want it > to run in, then what level of messages to display. I consistently answer > text/medium. It then preconfigures other packages, unpacks everything, and > starts the actual configuration phase. At this time, I am again asked what > mode I want debconf to run in and what message level to display.
I never saw this happen in all my testing of stable (hundreds of fresh installs). Nobody else has ever reported this either, nor have I seen this happen in the perhaps 10 installs of stable I have witnessed other people do. So believe it or not, it does work for most of us. If you can get a log of that with DEBCONF_DEBUG set, I would of course like to see it. > I just tried purging and reinstalling ssh on two machines. The one tracking > testing worked properly, only asking if I wanted it SUID and whether to run > sshd once. The one tracking stable asked 3(!) times. That version of apt > doesn't seem to like nonnumeric values for DEBCONF_DEBUG, so I tried setting > it to 100 instead, which seems to have worked. Well, this is ssh's breakage, seemingly limited to stable: > debconf: <-- FSET ssh/upgrade_to_openssh isdefault false Thus forcing debconf to redisplay the question each time. Any others? (And don't cite console-data, or cvs. Both have historically had the same breakage in stable.) -- see shy jo
