yes, this is expected behavior when using debconf; I should have foreseen the problem. Will be fixed in the next upload.
yes, this is expected behavior when using debconf; I should have foreseen the problem. Will be fixed in the next upload.