Bug 847880

Summary:	tar-out should allow (or force) --numeric-owner
Product:	[Community] Virtualization Tools	Reporter:	Andy Lutomirski <luto>
Component:	libguestfs	Assignee:	Richard W.M. Jones <rjones>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	dyasny, mbooth
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-14 16:56:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andy Lutomirski 2012-08-13 21:54:51 UTC

tar-out uses human-readable owners, which is unfortunate if the user of the resulting tarball has a different /etc/passwd than the guest.

Comment 1 Richard W.M. Jones 2012-08-13 21:59:36 UTC

Implementation notes:

Since commit 98757e151ae8ad8d334f028690abcc85b91c73e5
it has been possible to promote non-optargs functions (like
guestfs_tar_out) by adding optional arguments.  So (in
libguestfs >= 1.19.19) it should be easy to add optional
arguments to the guestfs_tar_out call, encoding this and
other flags.

Another one mentioned was --exclude= (bug 847881).  A single
exclude parameter could be modelled as an OString in the
generator, but that wouldn't be very useful since you could
only use it once.  It's probably better to add OStringList
and do this properly.

Comment 2 Richard W.M. Jones 2012-08-14 14:51:58 UTC

Patches posted:
https://www.redhat.com/archives/libguestfs/2012-August/msg00054.html

Comment 3 Richard W.M. Jones 2012-08-14 16:56:40 UTC

I pushed a less broken version of this patch upstream
in libguestfs 1.19.30.