Bug#361872: debconf-copydb: Trashes debconf database in /target
On Tue, Jun 20, 2006 at 04:40:53PM +0200, Steinar H. Gunderson wrote:
> On Mon, Jun 19, 2006 at 08:57:02PM +0200, Steinar H. Gunderson wrote:
> > After some discussion on IRC, here's the updated patch.
> One change is needed yet; the current code in debconf-copydb simply turns off
> i18n support (since the old code couldn't handle that properly, it seems, or
> perhaps it's even older). Just nuke the setenv() line from debconf-copydb.c
> and we should be okay.
> BTW, Joey: There _are_ lots of non-UTF-8 strings out there, it seems -- it's
> unfortunate, but we can't nuke the support from debconf just yet. :-/
In case this is of interest for someone, here are some figure:
* There are 7 packages in unstable with Field-xx translated fields
(i.e. without encoding):
* There are 107 (180 in main + 5 in contrib + 2 in non-free) packages
in unstable with non UTF-8 (and non utf-8 :)) Field-xx.encoding
translated fields. Note that many packages need more than a simple
rebuild because they implemented the hack described in
to ease woody portability.
* There is no package with Field-xx.utf8 translated field, so the
applied fix looks safe.
IIRC cdebconf does only support UTF-8 on output too, so it cannot
replace debconf when run under a non UTF-8 locale.