[Vmdebootstrap-devel] Bug#834215: Original raw image no longer chowned when using --owner and --convert-cqow2

Christian Kastner ckk at debian.org
Sat Aug 13 07:46:53 UTC 2016


Package: vmdebootstrap
Version: 1.6-1
Severity: minor
Tags: patch

The fix for #831030:

> When using both --owner and --convert-qcow2 together, the resulting .img
> file must also be chowned to be useful. Otherwise, the owner will only
> be able to access the .raw file.

appears to be incomplete. While the .img file is being chowned now, the
.raw file no longer is.

Hence why I duplicated the support in #831030, but that was indeed not
clean. I have attached an alternative solution.

Or, perhaps the .raw file should just be removed? Is there any reason to
keep it around? I don't see much of a use case to keep both, especially
when qcow2 is explicitly being requested.

Regards,
Christian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Also-chown-raw-image.patch
Type: text/x-patch
Size: 1100 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/vmdebootstrap-devel/attachments/20160813/9ad16d8f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/vmdebootstrap-devel/attachments/20160813/9ad16d8f/attachment.sig>


More information about the Vmdebootstrap-devel mailing list