Mark Brown wrote: > On Tue, Mar 16, 2004 at 01:14:19PM -0500, Joey Hess wrote: > > Mark Brown wrote: > > > > During the installer run many packages (for example, setserial) appear > > > to get installed without their debconf configuration scripts being run. > > > This means that when the packages get upgraded they prompt for > > > configuration. > > > Incorrect, they are installed in the normal way but with the > > noninteractive debconf frontend. The config scripts run. Any package > > that behaves as you describe when installed this way is broken; this is > > It seems to be happening an awful lot - I'd suggest including some kind > of automated reinstall of all the packages in the testing of the > installer (next time I do an install I'll probably give this a whirl).
I can't imagine how it could happen at all without some great care being taken to make debconf behave in a way it truely does not want to, or a debconf behavior I am not anticipating. Can you provide an example of a debconf database before the upgrade, plus the upgrade with DEBCONF_DEBUG='.*' ? -- see shy jo
signature.asc
Description: Digital signature
