[James Valleroy] <jvalle...@mailbox.org> writes: > I think we can avoid this by always removing the policy-rc.d, even if it > wasn't created during this setup run.
This will break setup in a pre-existing chroot. We need to know if we set it up and remove it only then. Perhaps add a marker in the file and only remove it if the marker is present? Or rewrite the code to not leave the file behind if any of the scripts fail? -- Happy hacking Petter Reinholdtsen
