Bug#208408: tetex-bin: No hyphenation patterns were loaded

[frank@kuesterei.ch (Frank Küster)]

Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp> schrieb:

> From: frank@kuesterei.ch (Frank Küster)
> Subject: Bug#208408: tetex-bin: No hyphenation patterns were loaded
> Date: Wed, 10 Sep 2003 19:47:57 +0200
>
>> I have tried the following. Concerning defaults and preserving old
>> choices, it does what it was made for. However, there's one problem I
>> don't understand: The hyphen question is always shown twice. The second
>> time seems to be just before postinst is started, or at its very
>> beginning. 

This comes from setting seen flags without completely understanding
debconf-devel(7). The config is run again when postinst is run, to
provide a backup method. If setting the seen flag to false is done
unconditionally, it is done again in the second run, and the question is
asked again.

The solution would be to either

- create a new template that will never be seen, and store in it the
  information whether the question has been (succesfully) asked) or

- create a new flag to the question for this task.

The second seems nicer to me, but I will have to learn how to do it.
>
> I didn't tested the patch yet but 
>
> - did you remove debconf stuffs in preinst?

No, I didn't change anything in preinst.

> - it seems "db_fset tetex-bin/hyphen seen false" without
>   any version condition which means debconf question will
>   be shown any upgrade.  Is this your intention?

Uups, I overlooked this. We have the following cases (calling the next
release 2.0.2-5 for clarity, not because I would object to
4.4). Everything assumes that the user chose that language.dat be
managed by debconf, all conditional are inside this main "if":

a) Upgrading from stable to >=2.0.2-5: Flag is set to unseen in any case

b) Upgrading from testing/unstable =<2.0.2-4.3 to >=2.0.2-5: Question
   has to be shown even if answered before.

c) Upgrading from $Version>=2.0.2-5 to $Version-new>$Version: Question
   should not be asked again.

This means the flag-fiddling will have to persist in future versions,
but with an additional check if this has been done. We can easily
achieve this in the same way how we prevent the question from being
shown two times upon the same upgrade (see above).

Bye, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie