Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-21 Thread Denis Barbier
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

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-20 Thread Joey Hess
Frans Pop wrote: > The only remaining issue is that after the debconf-copydb all "Owners:" > fields from the original templates.dat in target are lost. This might be because cdebconf and debconf track template use in different ways. Not sure how to fix this, and messing with debconf's template us

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-20 Thread Frans Pop
(Keeping Steinar in To: in the hope he'll want to try this one as well ;-) On Tuesday 20 June 2006 16:40, you wrote: > 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 ol

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-20 Thread Steinar H. Gunderson
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 ev

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-20 Thread Frans Pop
On Monday 19 June 2006 20:57, Steinar H. Gunderson wrote: > After some discussion on IRC, here's the updated patch. Joey applied this patch yesterday and today I've built cdebconf for the new version and after that a mini.iso including that. When pkgsel is run, the debconf database is still being

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-20 Thread Steinar H. Gunderson
On Tue, Jun 20, 2006 at 03:31:14PM +0200, Frans Pop wrote: > Joey applied this patch yesterday and today I've built cdebconf for the > new version and after that a mini.iso including that. > When pkgsel is run, the debconf database is still being trashed... > > /me is confused Ouch, that's not g

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Denis Barbier wrote: > > After some discussion on IRC, here's the updated patch. > > > > --- cdebconf-0.102.orig/src/template.c 2005-09-21 19:07:46.0 > > +0200 > > +++ cdebconf-0.102/src/template.c 2006-06-19 20:54:35.0 +0200 > > @@ -354,7 +354,7 @@ > > fre

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Denis Barbier
On Mon, Jun 19, 2006 at 08:57:02PM +0200, Steinar H. Gunderson wrote: > On Mon, Jun 19, 2006 at 01:42:53PM -0400, Joey Hess wrote: > > The easiest way would probably be to not track the information and store > > (and output) the field as utf-8 without doing any transcoding. This is > > not exactly

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 09:58:17PM +0200, Denis Barbier wrote: > I am not sure that this is desirable, next time you will encounter "utf8" > instances, and maybe other names too (except that I cannot find another > one ;)) Well, either we'll have to keep adding special-casing of UTF-8, or we'll ha

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:42:53PM -0400, Joey Hess wrote: > The easiest way would probably be to not track the information and store > (and output) the field as utf-8 without doing any transcoding. This is > not exactly what debconf does, but fields that do not define an encoding > are basically u

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
First of all, this is a bit of a side issue since as noted any reasonable current package that's translated with po-debconf is going to use proper utf-8 fields. Steinar H. Gunderson wrote: > Well, debconf-copydb does: > > - Read in first and second config.dat. > - Read in first and second tem

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:23:17PM -0400, Joey Hess wrote: >> What do you propose in this case -- hacking support for this kind of >> "undefined encoding" stuff into cdebconf? > No, I don't think that cdebconf should worry about supporting this stuff > beyond not corrupting it if reading a debconf

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Steinar H. Gunderson wrote: > Well, some of the fields seem to be ASCII; some of them are UTF-8. > > What do you propose in this case -- hacking support for this kind of > "undefined encoding" stuff into cdebconf? No, I don't think that cdebconf should worry about supporting this stuff beyond not

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Joey Hess
Steinar H. Gunderson wrote: > shouldn't be all that hard), but I don't think one would want pulling iconv > into d-i, and I've never seen any templates _not_ in UTF-8 or ASCII, so I > guess it would be a bit pointless. However, it special-cases fields like > "Description-xx.UTF-8", so this should r

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Mon, Jun 19, 2006 at 01:10:47PM -0400, Joey Hess wrote: > If it's using ascii that's valid, anyway cdebconf should also be sure to > copy Description-xx[_XX] fields too, as debconf will store them that way > if the package doesn't specifiy an encoding. Well, some of the fields seem to be ASCII;

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-19 Thread Steinar H. Gunderson
On Thu, Jun 15, 2006 at 10:44:23PM +0200, Frans Pop wrote: > The relevant files (hope the filenames speak for themselves) and an strace > are available from: > http://people.debian.org/~fjp/d-i/debconf-copydb.tgz > (uploaded instead of attached because of size) I figured out the bug. If you tweak

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-15 Thread Frans Pop
On Thursday 15 June 2006 21:33, Steinar H. Gunderson wrote: > > Another is busybox. > > How would this influence anything? Told you they were _wild_ guesses ;-) > Do you have a copy of the source and target databases, as well as the > cdebconf.conf used? It might be something specific about the d

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-15 Thread Steinar H. Gunderson
On Thu, Jun 15, 2006 at 07:29:44PM +0200, Frans Pop wrote: > I can still reproduce the problem during an installation though... Ugh. Could you provide an strace of it, or would that be too much of a hassle? > One idea is the encoding (installer is running with nl_NL.UTF8, although > the pkgsel p

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-15 Thread Frans Pop
On Sunday 11 June 2006 20:04, Steinar H. Gunderson wrote: > I'm unable to reproduce this with 0.102 in a normal (ie. non-d-i) > environment: I can still reproduce the problem during an installation though... > configdb is here set up to be my normal debconf database (so I have > some source data

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-06-11 Thread Steinar H. Gunderson
On Mon, Apr 10, 2006 at 11:42:29PM +0200, Frans Pop wrote: > When debconf-copydb is run from pkgsel's postinst script, it deletes the > existing /var/cache/debconf/templates.dat in /target; after it has run > only copied templates are present. > > This results in the problem that has been report

Bug#361872: debconf-copydb: Trashes debconf database in /target

2006-04-10 Thread Frans Pop
Package: cdebconf Version: 0.97 Severity: serious When debconf-copydb is run from pkgsel's postinst script, it deletes the existing /var/cache/debconf/templates.dat in /target; after it has run only copied templates are present. This results in the problem that has been reported that tasksel is