Bug#361872: debconf-copydb: Trashes debconf database in /target
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 postinst sets and exports LANG=C).
I'm running with en_DK.UTF-8 myself, so I doubt it is the encoding.
> Another is busybox.
How would this influence anything?
> A third is the way debconf-copydb is called within d-i; maybe broken
> handling if the target is target_configdb?
I'm running with target_configdb myself, so I doubt the latter is the case,
but yes, it appears very d-i-specific somehow...
> The full call is:
> debconf-copydb -p \
> "^(debian-installer/language|debian-installer/country|
> debian-installer/keymap|passwd/username)$" \
> configdb target_configdb
trofast:~# grep Name: /target/var/cache/debconf/templates.dat
Name: acpid/modules
Name: acpid/noacpi
Name: apache-common/confignotes
Name: apache-common/logs
Name: apache-common/old-logrotate-exists
Name: passwd/username
trofast:~# /usr/lib/cdebconf/debconf-copydb -p "^(debian-installer/language|debian-installer/country|debian-installer/keymap|passwd/username)$" configdb target_configdb
trofast:~# grep Name: /target/var/cache/debconf/templates.dat
Name: acpid/modules
Name: acpid/noacpi
Name: apache-common/confignotes
Name: apache-common/logs
Name: apache-common/old-logrotate-exists
Name: passwd/username
In other words, no big surprises here (my debconf database doesn't have any
d-i keys).
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 data in the
destination that makes cdebconf discard it...
/* Steinar */
--
Homepage: http://www.sesse.net/
Reply to: