If a user runs Beagle on their system and Beagle indexes a file, if you try to copy that file to say a FAT formated USB Disk (as most are), the copy will fail and give a bunch of errors. Robert Love has a proposed patch for attr which I'm including here. Instead of $ cp x /var/tmp cp: setting attribute `user.Beagle.Uid' for `/var/tmp/x': Operation not supported cp: setting attribute `user.Beagle.MTime' for `/var/tmp/x': Operation not supported cp: setting attribute `user.Beagle.IndexTime' for `/var/tmp/x': Operation not supported cp: setting attribute `user.Beagle.Fingerprint' for `/var/tmp/x': Operation not supported I fixed it. We now have $ cp x /var/tmp cp: Metadata will be lost, setting attributes for `/var/tmp/x': Operation not supported Looks like attr is only pulled into coreutils with the acl USE flag... even though attr is used for more then just ACLs... but oh well.
Created attachment 59395 [details, diff] attr_copy_file-suppress-warning.patch
*** Bug 93389 has been marked as a duplicate of this bug. ***
added to attr-2.4.19-r1