Mark Brown wrote: > I've found some more instances of this problem. I managed to catch a > diff of the config files before and after the upgrade, though I didn't > remember to rerun the upgrade or cache the entire database: Now I understand. This is because debootstrap installs packages using the noninteractive frontend which does not set questions to seen as the user has indeed not seen them. It's true that this could lead to some questions that have already set and presumably working values being asked on upgrade. I don't know of a good way to avoid this at this time; debconf's handling of the seen flag for the noninteractive frontend is basically correct; debootstrap's use of the noninteractive frontend is correct, and there's no way d-i can go back after the fact and mark questions as seen. -- see shy jo
Attachment:
signature.asc
Description: Digital signature