On Mon, 15 Dec 2003, Brian McGroarty wrote: > On Mon, Dec 15, 2003 at 06:28:37PM -0600, Adam Heath wrote: > > On Sat, 13 Dec 2003, Brian McGroarty wrote: > > > > > Package: dpkg > > > Version: 1.10.18 > > > Severity: important > > > > > > dpkg proceeds even if the preconfigure scripts do not successfully run. > > > > dpkg is not running that. debconf is. Which is either called by apt > > directly(preconfigure), or by a package's preinst/postinst. If it's the > > latter case, it's a bug in the package. > > > > So, what package are you having problems with, so that this bug can be > > reassigned to it. > > This happened during the preconfigure stage after using dselect. Do > you know whether dselect works through apt, or whether should this be > a dselect bug? > > Thanks, Adam.
It depends if you have choosen apt as the access method. Again, this isn't a bug in dselect, dpkg, apt, or debconf. It's a bug in the exact package's maintainer scripts. If dpkg-preconfigure(part of debconf) is not displaying the package name when errors occur in the config script, then file another bug on debconf in that case. If it is, then say so, and this bug can be reassigned to the correct package.
