pax lack of support for "pax" format fails LSB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MirCPIO |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The SUS/POSIX standard tool pax is required for LSB 3.2 compliance. The
version of this tool on Linux (all systems I've tested) provide ustar format
but not 'pax" format. "pax" format is required by LSB; it is needed to backup
ACLs and extended attributes including SE Linux labels.
libarchive does support pax format. It should be easy to create a front-end
for pax that uses libarchive (which comes with bsdcpio front-end, but not in
the Fedora 10 package). SUSv3 and SYSv4 (and POSIX all required this format to
be supported, and LSB 3.2 does as well.) Not supporting it means no standard
tool can make archives with EAs; more importantly it means Fedora (and
presumably Red Hat) is not compliant with the LSB.
How reproducible:
Always
Steps to Reproduce:
try "pax -x pax" ...
Actual results:
pax: Unknown -x format: pax
Expected results:
should work.
Additional:
I originally reported this against Fedora. The maintainer, <email address hidden>, confirms no distro
supports this and has written a patch. (See Fedora bug #503860.) But libarchive supports this
so I think it should be fairly easy to lift that code, or just invoke that .so from pax?
affects: | ubuntu → ubuntu-meta (Ubuntu) |
There are two separate but related issues here:
1. the pax utility doesn't support the pax format (a LSB conformance bug in pax)
2. the pax utility isn't installed by default (a LSB conformance bug in ubuntu-meta)
This bug report seems to be about the first issue, so I'm moving this to pax. A separate bug should be opened for the second issue.