On Mon, Jan 18, 2010 at 05:48:10PM +0000, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > Bug reassigned from package 'exim4' to 'schroot'. > Bug #565613 [schroot] exim4: syntax error: unknown group 'Debian-exim' in > statoverride file > Bug Marked as found in versions schroot/1.2.3-1. > > retitle 565613 overwrites customized /etc/passwd and /etc/group > Bug #565613 [schroot] exim4: syntax error: unknown group 'Debian-exim' in > statoverride file > Changed Bug title to 'overwrites customized /etc/passwd and /etc/group' from > 'exim4: syntax error: unknown group 'Debian-exim' in statoverride file'
Thanks for the report. schroot can not (does not) support running dæmons such as exim. At least, not sensibly. The chroot does not by default have any running daemons such as syslog, and the init scripts need invoking manually. Lastly, unless you're using the "plain" chroot type, the chroot will be umounted when schroot terminates (or the session is ended), and all running processes in the chroot are terminated prior to this. That said, this is definitely a bug, though the severity is debatable. For most uses of schroot, the existing default is appropriate. It's not a separate system from the host, so using the same system databases is OK. What's not OK is losing data inside the chroot. We could add logic to compare the two and merge the differences rather than using the existing approach of replacing the whole lot. But, there would be issues of having different accounts with the same UID/GID where dynamically added entires conflict between the host and the chroot. For now, I would suggest disabling the update in your specific case. Any suggestions about how best to solve this would be appreciated, and patches even more so. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature