bpo-39688: tarfile: compute next header offset using pax size for sparse file#18562
bpo-39688: tarfile: compute next header offset using pax size for sparse file#18562nitmir wants to merge 2 commits into
Conversation
…rse file In case of a sparse file, the tarinfo.size attribute is set to the sparse file expanded size (pax attribute GNU.sparse.size or GNU.sparse.size) and do not correspond to the actual size of the data block. The size of the data block is specified by the size pax header if present or by the ustar size header. Moreover, for GNU sparse 1.0 files, the data block start at the beginning of the sparse mapping and not after the sparse mapping and so the offset should be computed from here.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
This PR is stale because it has been open for 30 days with no activity. |
In case of a sparse file, the tarinfo.size attribute is set to the sparse
file expanded size (pax attribute GNU.sparse.size or GNU.sparse.size) and
do not correspond to the actual size of the data block. The size of the
data block is specified by the size pax header if present or by the ustar
size header.
Moreover, for GNU sparse 1.0 files, the data block start at the beginning of
the sparse mapping and not after the sparse mapping and so the offset should
be computed from here.
https://bugs.python.org/issue39688