On 12/22/2010 02:10 AM, jor...@linuxgen.com wrote: > On Tue, Dec 21, 2010 at 10:44:42PM +0100, Alban Browaeys wrote: >>> So you are saying that the script should *fail* if it is a first >>> installation of ntop and there is not ask to ask the user? >>> >>> The only concern about that it is that it would prevent automated >>> installs... >> >> I am thinking in such case the user should preseed via fai or such. >> Also sorry I forgot to add a check for empty "password again" > > I agreee that the use case here would be via preseeding or fai, however, we > don't need the postinst to fail.
I agreed. Let's avoid setting the ntop password and not fail in the postinst. ntop will not to start but installation will not fail. >>> Do you have points againts setting random password in this case? >> no. This is a short term fix. Also the issue I encountered was not with >> automated install but merely the second db_input not triggering a dialog >> on second call with default settings for debconf. So we probably want >> both fix (ie check that the password again was not already asked on >> reinstall and a random password on unattended first installs). Yes, we ended up talking about 3 different issues. This first one is already fixed in the git repository. My bad using this bug report to start discussion. This is not the place. Let's stop it here. > I think the reason that the second db_input was not trigger was because I > did not set "seen" to false. > > db_fset ntop/admin_password seen false > db_fset ntop/admin_password_again seen false Yes, I think this is an issue, but an additional one :) Thanks, Ludovico -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
