On 3/17/24 7:45 PM, Tim Kientzle wrote:
> GNU tar could choose to ignore that particular attribute without issuing a
> warning.
I'm happy with that behavior if there are objections.
This diff seems to work with that archive. I'm not familiar with GNU
tar or even the ustar for that matter though, so I may be missing
something.
diff --git a/src/xheader.c b/src/xheader.c
index e2b124b8..d00b0c90 100644
--- a/src/xheader.c
+++ b/src/xheader.c
@@ -1761,6 +1761,9 @@ struct xhdr_tab const xhdr_tab[] = {
{ "GNU.volume.offset", volume_offset_coder, volume_offset_decoder,
XHDR_PROTECTED | XHDR_GLOBAL, false },
+ /* Unused. */
+ { "LIBARCHIVE.creationtime", dummy_coder, dummy_decoder, 0, false },
+
/* We get the SELinux value from filecon, so add a namespace for SELinux
instead of storing it in SCHILY.xattr.* (which would be RAW). */
{ "RHT.security.selinux",
> bsdtar’s `--no-xattrs` option suppresses filesystem extended attributes
> (“xattrs”). Creation time is not an xattr.
>
> I would suggest instead `--format ustar` to create maximally-portable
> archives that do not contain any pax extensions. This works with both bsdtar
> and GNU tar.
Oops, I saw someone reported this archive to eclipse and said
--no-xattrs would silence it [1]. I'll update the report and let them
know --format ustar would be the correct option. Thanks for the advice!
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=582413
Collin
