Ralf Stubner <[EMAIL PROTECTED]> wrote:
> Frank, should some more information be given to the admin in the
> noninteractive case? tex-common's postinst failing without any
> indication as to what's wrong doesn't look ideal to me.
It might be related to these debconf changes:
debconf (1.5.1) unstable; urgency=low
[ Joey Hess ]
* Stop mailing notes since something like 90% of the use of that data type
is abuse anyway. Error messages will still be mailed if necessary.
debconf (1.4.69) unstable; urgency=low
[ Colin Watson ]
* Add support for templates of type 'error', which are largely treated
like notes except that they are displayed no matter what the priority
and even if they've previously been seen. For example, this can be used
for input validation errors. This is compatible with cdebconf.
I've never bothered to check this, because I don't receive mail in my
pbuilder chroots ;-). But anyway, we should try to detect whether the
frontend is noninteractive, and output something on stderr in that
case. But how to do that?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
