On Thu, Nov 16, 2006 at 08:24:50AM +0100, Mario 'BitKoenig' Holbe wrote: > On Wed, Nov 15, 2006 at 11:01:51PM -0800, Steve Langasek wrote: > > On Wed, Nov 15, 2006 at 04:38:39PM +0100, Mario 'BitKoenig' Holbe wrote: > > > gradm version 1.9.15-2.1 fails to install: > > Are you trying to use the non-interactive front-end?
> for debconf? No, my debconf frontend is Dialog. > I think the failing postinst is because the postinst script does only > contain: > #!/bin/sh -e > . /usr/share/debconf/confmodule > nothing more. And I assume this returns something != 0 no matter what > debconf frontend is used. 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. Since the input happens at critical priority in debconf, the obvious explanation would have been that you were using the non-interactive frontend. The config script is buggy anyway, since the question will only be displayed /once/, and db_input will be called /twice/ during an apt upgrade... I just don't understand why the pre-configuration also failed in your log. Cheers, -- 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]
