tags 397214 -patch thanks On Tue, 14 Nov 2006 23:16:03 +0000 (GMT) Matthew Johnson <[EMAIL PROTECTED]> wrote:
> For more detail, what actually happens is that the config file is > regenerated on upgrade from the original debconf questions. This is not true. It is regenerated from what is in the config file and any new answers. If you read the code carefully you see that it fills all the question with the values from the file. (except for splash, which is the real bug) > b. several of the questions are not asked by debconf because of their > priority. It's not immediately obvious how these should be configured > since dpkg-reconfigure still doesn't ask them due to their debconf > priority (in particular splash). The priority has nothing to do with it, the splash question is not asked at all. This is because splash was not supported yet. The current splash only works with the bootsplash kernel patch, which isn't applied to the debian kernel. I added the splash question because I've written a userspace splash library which can also be linked to uswsusp, but it isn't in debian yet. > It's not clear that the automatic generation should happen more than > once; I think it should happen only if the config file doesn't exist. No. That way people can't use dpkg-reconfigure. Using dpkg-reconfigure is convenient because that will also regenerate the initramfs and the encryption keys if you asked for it. To summarize, you bug is a different one. It sneaked in because splash was not supposed to be supported yet, but apparently you are using a patched kernel. The solution is very simple and is already in my svn. It will be included in the next upload. grts Tim
signature.asc
Description: PGP signature
