On Mon, Jan 18, 2010 at 06:45:23PM +0000, Roger Leigh wrote:
The problem was not running it, but removing it (because it used dpkg-statoverride with a "custom" group). It was installed via some dependency chain (about any non-trivial installation pulls in an MTA and exim4 is the default, for better or worse).schroot can not (does not) support running dæmons such as exim.
That would be the golden way of course. In practice I think it would suffice to have schroot detect that the files inside the chroot have been changed (by comparing with a stored checksum) and refuse to overwrite them (with an appropriate warning printed).We could add logic to compare the two and merge the differences rather than using the existing approach of replacing the whole lot.
At the very least the defaults should be commented out with a warning what might break.
CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/
signature.asc
Description: Digital signature
