This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: tarfile.py and multiple extended headers
Type: Stage:
Components: Library (Lib) Versions:
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: akuchling Nosy List: akuchling, lars.gustaebel
Priority: normal Keywords: patch

Created on 2004-07-10 11:37 by lars.gustaebel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
subsequent-xheaders.patch lars.gustaebel, 2004-07-10 11:37 patch against Lib/tarfile.py
Messages (2)
msg46334 - (view) Author: Lars Gustäbel (lars.gustaebel) * (Python committer) Date: 2004-07-10 11:37
At the moment, tarfile.py is only able to read one
extended/special header (such as GNU longname etc.) at
once from an archive. In some cases there may be more
than one special header to process, e.g. an archive
member that points to a long linkname itself having a
long name, or a GNU sparse file member with a long
name. In those cases tarfile.py will fail to read that
particular member including all following ones. The
attached patch fixes that problem plus some minor
things that I came across while fixing it:

- fixed/improved handling of extended/special headers
in read-mode (adding new extended headers should be
less painful now).
- improved nts() function.
- removed TarFile.chunks datastructure which is not
(and was never) needed.
- fixed TarInfo.tobuf(), fields could overflow with too
large values, values are now clipped.

The patch is made against 2.4a1 sources.
msg46335 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2004-07-10 22:02
Logged In: YES 
user_id=11375

Applied to CVS HEAD; thanks!
History
Date User Action Args
2022-04-11 14:56:05adminsetgithub: 40532
2004-07-10 11:37:47lars.gustaebelcreate