catalyst-2.0.18 added the following options to the various tar commands invoked during the stage builds: --xattrs --xattrs-include=security.capability --xattrs-include=user.pax.flags --acls --selinux Using these on a filesystem that does not have ACL or xattr support enabled leads to very noisy output: tar-1.28.tar.bz2 tar: XATTR support is not available tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/acinclude.m4': Operation not supported tar: SELinux support is not available tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/ChangeLog.1': Operation not supported tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/config.h.in': Operation not supported tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/Make.rules': Operation not supported tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/doc/value.texi': Operation not supported tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/doc/rendition.texi': Operation not supported tar: acl_set_file_at: Cannot set POSIX ACLs for file 'tar-1.28/doc/fdl.texi': Operation not supported [truncated] Not sure of a good way to handle this, so I don't have a patch available. I modified my local copy of catalyst to remove these params from the tar calls as a hack. Probably some kind of switch in catalyst.conf might work, with an appropriate default.
I should add, this appears to happen on an XFS filesystem lacking ACL support. ext3/ext4 filesystems only print the errors about missing XATTR and ACL once, but under XFS, the ACL errors are printed once per file extracted.
as noted somewhere else, i don't think any official release media should be built w/out xattrs. i have no problem with making support optional for users for their own builds however.
(In reply to SpanKY from comment #2) > as noted somewhere else, i don't think any official release media should be > built w/out xattrs. i have no problem with making support optional for > users for their own builds however. Well, MIPS stages for the SGIs are experimental anyways, and xattr support is going to depend on the underlying host filesystem, of which none of my build machines use xattr at all. And I'm still hamstrung by that ncurses mess-up a while back on my Octane anyways. I'd say make the support optional within catalyst, but defaulted to on, and update the releng guides to indicate that official/stable release media needs to be built with the support enabled.
This is in git now. New spec file options: compressor_options: compressor_arch: Default linux compressor_options are the current xattr options. Adding this option to hte spec file will override the defaults. setting compressor_options: None will remove any defaults and add no additional options to the definitions.
