> 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.
The following patch should fix the problem: --- config.old 2006-11-16 18:20:37.240504995 +0100 +++ config 2006-11-16 18:20:43.732625313 +0100 @@ -2,5 +2,5 @@ . /usr/share/debconf/confmodule -db_input critical gradm/deprecated +db_input critical gradm/deprecated || true db_go I think that this problem popped up because the former version.....was missing a call to confmodule and then never executed the config script...so my lintian fixes to add a postinst script just revealed an existing bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
