Control: retitle -1 dbc should propagate more error messages to debconf Control: tags -1 confirmed Control: summary 0 I think that dbconfig-common could record the error message in locations where it currently doesn't and display it in the debconf error template (or at least part of the error message if it is long). If that doesn't work, I think that at least the template should be updated to describe the actual error message can be found in the apt-get log.
On Sat, 22 Nov 2008 09:01:09 +0200 Niko Tyni <[email protected]> wrote: >> Also note that I had to change the dbconfig-common file below to be >> able to see the error, otherwise debconf would just replace it and >> hide the error. I removed the "exec" word and added a sleep 5 as >> last line of the script. > > I think this is worth another bug, cloning. Just a side note, there are multiple frontends to debconf, the one causing this hide problem is just one of them. All output remains visible if you use for example: DEBIAN_FRONTEND=readline Also the /var/log/apt/term.log file should contain the error message. > It should probably be fixed in dbconfig-common too by improving > logging of the script call or at least sleeping a bit before invoking > dbc_install_error(). I don't think sleeping is a good idea. Usually the error will still not be seen as I don't think most admins are constantly monitoring the process (at least I usually don't). However, I do think that dbconfig-common could record the error message in locations where it currently doesn't and display it in the debconf error template (or at least part of the error message if it is long). If that doesn't work, I think that at least the template should be updated to describe the actual error message can be found in the apt-get log. Paul
signature.asc
Description: OpenPGP digital signature
