Bug#748477: vmdebootstrap: images should not always be owned by root

On Sat, May 17, 2014 at 11:01:11AM -0500, Nick Daly wrote: Package: vmdebootstrap Version: 0.2-2das-boot2 Severity: normal Dear Maintainer, When vmdebootstrap completes, the generated images are always owned by the root user. This is very inconvenient for automated builds which need

Bug#748477: vmdebootstrap: images should not always be owned by root

Antonio Terceiro terce...@debian.org writes: What's wrong with running chmod on the built image as part of your automated build? That was my first thought. However, because root owns the image, I'd have to either: - Build the image as root to chmod the image, or, - Give the building user

Bug#748477: vmdebootstrap: images should not always be owned by root

Package: vmdebootstrap Version: 0.2-2das-boot2 Severity: normal Dear Maintainer, When vmdebootstrap completes, the generated images are always owned by the root user. This is very inconvenient for automated builds which need to be able to operate on the built image file. The attached patch

Bug#748477: vmdebootstrap: images should not always be owned by root

The previously mentioned patch is attached to this email. Apologies for the noise. Nick --- vmdebootstrap 2014-05-11 13:16:27.948314432 -0500 +++ /usr/sbin/vmdebootstrap 2014-05-10 14:26:22.0 -0500 @@ -100,6 +97,9 @@ self.settings.boolean(['sudo'],