Comment 3 for bug 1093973

This issue is already being tracked in the following bug reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565613
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557730

Note that this has been the default behaviour since schroot was written. What has changed which might have affected you is that older versions had the option to disable the setup scripts for all chroot types; they are now always run for all types except "plain" (which is identical to "directory" except that no setup scripts are run). Note that this is only the /default/ behaviour--what's copied is entirely configurable if this does not meet your needs.

This is definitely a problem, but it's not entirely clear what the best solution (or set of solutions) we need. Most chroot environments need the NSS databases syncing from the host, or else the entries for the current user etc. won't be present. The purpose of schroot is to automate this, rather than requiring manual updates by the admin. This works fine until you want something different in the chroot, or you add things inside the chroot which are then subsequently lost; however, synchronising this data one (or two) ways between the host and guest is decidedly non-trivial.

For the time being, it's simple enough to disable the behaviour: just edit /etc/schroot/$profile/nssdatabases (and/or copyfiles) and comment out the databases/files you don't want to be copied. Or you could create your own custom profile rather than modifiying one of the pre-canned profiles.

I'll look at making your suggested changes to the documentation.

If you could follow up to the original Debian reports rather than here, that would be appreciated. Thanks.

Regards,
Roger