Hi all, I have finally sorted this all out.
Frank Küster <[EMAIL PROTECTED]> wrote: > The strange thing is that it is so hard to reproduce. It depends on the > precence of apt-utils, this is true... > so it means it depends on whether the config > script is run on its own (before preinst), or is sourced from the > postinst script. But this not. The true reason is that with apt-utils, the config script is actually run twice: Once before preinst, and once from the postinst script, as without apt-utils. This is always the case, and it's one more reason why maintainer script need to be idempotent (behave the same if run several times). Ours wasn't idempotent, but i have already fixed this: The reason was the same why the default "cache" wasn't displayed on a fresh install, or in other words our unconditional db_set call, even if no ls-R files are present. So what I need to do now is to create proper ls-R files (with the magic comment) if they don't exist, prior to chmod'ing. Should I also create the ls-R-files that are not managed by debconf? I think we should leave this to mktexlsr. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer