also sprach Tore Anderson <[EMAIL PROTECTED]> [2005.05.25.1814 +0200]: > Even with this patch applied, I would think the bug would still appear > with DEBIAN_FRONTEND=noninteractive, no?
Yes, and then we have a problem because there simply is no default
for a password, is there? And I refuse to create a default password.
An alternative would be to accept an empty password, render zope
unstartable until the password is set, and display a message to this
effect (which would be mailed if noninteractive was set).
This might not be trivial, but I think it would be the best
solution...
zope2.7 handles this by not creating an instance in postinst. We
will use the same approach also for zope 2.6, but not before sarge.
Anyway, do people want me to fix this? If so, how?
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, admin, user, and author
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
sed -e '/^[when][coders]/!d' \
-e '/^...[discover].$/d' \
-e '/^..[real].[code]$/!d' \
/usr/share/dict/words
signature.asc
Description: Digital signature
