Joey> This is not a template error, and is not a debconf bug. What we Joey> have here is a config script that, due to several typos in it Joey> outputs garbage to stderr. What you are asking is that debconf Joey> either display the name of the package containing each config Joey> script it runs (which would be a lot of typically unnecessary Joey> output), or somehow figure out that a config script is going to Joey> or has output something to stderr, and helpfully print out the Joey> package it comes from. Neither of these are at all appealing.
What about testing the scripts error codes ? Joey> Since the config script runs again when dpkg installs the Joey> package, you are always assured of being able to tell what Joey> package it's in at that point. Unfortunately I did not see the other error message because I was running apt/dpkg from dselect and I had to hit Ctrl-z at some point which gives very bad results :>. Joey> Nope, this config script turned on perl warning and passed an Joey> undefined value into a perl module which it used. That could have Joey> been any perl module and the results would have been similar. Is it possible to display a perl backtrace when such warnings occur ? -- Laurent.
