On Thu, Nov 16, 2006 at 02:36:34PM +0100, Mario 'BitKoenig' Holbe wrote: > On Thu, Nov 16, 2006 at 05:12:59AM -0800, Steve Langasek wrote: > > No, the postinst is fine; the failure is in the config script which it > > calls, whose error exit propagates to the postinst. > > An exit code of 30 happens if the message isn't displayed to the user.
> Hm, if the call to /usr/share/debconf/confmodule in postinst exits 30 > because gradm/deprecated isn't (yet) displayed to the user, No, it exits because db_input is supposed to *display* it to the user as necessary, and the return value informs the caller whether this is actually done -- in the general case you get a 30 return /after/ it's been shown to the user, since the first time it's called is normally when it does get displayed... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
