On Fri, Feb 22, 2002 at 03:43:04AM -0500, Joey Hess wrote: > > 1. change nothing and abort like we do now > > 2. do not create the database and use a debconf note to inform the > > administrator his slapd was installed but can't be used currently. > > I really don't want to do that though, since this basically > > means falsely telling the packaging system slapd was installed > > properly > > 3. generate a random password ourselves and use a debconf note to > > inform the administrator that that password was used > > > > Does anyone have any opinions on what to do? I'm tempted to implement > > the third option. > > I'd suggest doing 2. but after dropping the note, hae the postinst fail, Then we have #1 with different text, and this bug opens again. The postinst should not fail in this case. > By the way, this is making me think that debconf noninteractive mode > should perhaps display notes to the console besides mailing them. Perhaps, but a way to turn that off would be useful as well for cases like debootstrap, or truely unattended updates. -- Ryan Murray, Debian Developer (rmurray@cyberhqz.com, rmurray@debian.org) The opinions expressed here are my own.
Attachment:
pgp0ScXeJt7ba.pgp
Description: PGP signature