Thanks. That is what I thought you were asking for. There are several
downsides to your proposal as I see it: 1. having extra files in the
destination directory which were not created by vmbuilder will be more
confusing, 2. 'if something does not work (due to permissions or other
issues), blame
** Changed in: vm-builder (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1044837
Title:
vmbuilder should accept an empty destination
Sorry for the unclear description of the bug.
The manpage says:
-o, --overwrite
Force overwrite of destination directory if it already exist.
[default: False]
But apparently vmbuilder does not overwrite it. It tries to delete it (which
fails with mountpoints) and then recreat
Thanks for reporting this bug.
Adding such a check seems to complicate the existing check for little
real gain. If /srv/kvm/mysql is a mount point, is there a reason why
you could not use '/srv/kvm/mysql/mysql' as the target directory? (If
your use case isn't easily solved that way, then I'm ope
