On Thu, Nov 16, 2006 at 06:23:40PM +0100, Christian Perrier wrote: > > 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. Well, the old version would still execute it in the pre-configure stage, and would fail then, but a failed pre-configure is non-fatal. BTW, given the contents of this debconf message, is it better to remove the package anyway...? -- 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]
