On Mon, Oct 28, 2024 at 12:52 PM Robert B. Carleton <r...@rbcarleton.net> wrote: > I think pax(1) may be mis-attributing errors to Ustar when using other > formats. I've been seeing this kind of error when using the pax format: > > "pax: Ustar cannot archive a socket /home/example/.cache/at-spi/bus_0"
Yeah, the 'pax' format is "ustar, but with special 'g' and 'x' records" so it mostly uses the ustar routines when working with pax archives. Maybe those shared routines could look up which format is actually in use and use that in warning messages. Might be a reasonable intro fix for someone... Philip Guenther
