Closed gravicappa closed 1 year ago
Good catch! I confirmed this by checking the code and testing.
I am working on some major breaking changes, and there are already some breaking changes in the API. Would you like a backported fix, or are you okay with waiting?
(I will submit my changes soon as they have been sitting on my computer for a while)
Thanks for a quick response! A backported fix would be nice as I am unsure in soundness of my own workaround.
Ok! Note that it will not consider the pax global header -- though that is unlikely to affect file names, but can affect ownership and such.
I will likely not be able to do a release with a fix before Friday this week.
Hi @gravicappa, tar.2.5.0 has been released with a fix.
Tar.Header.unmarshal
ignoresextended.path
andextended.link_path
. I think those values (if exists) should replace header'sfile_name
andlink_name
fields.This issue breaks reading archives that has
x
headers containingpath=
entries since it returnsTar.Header.t
withfile_name
values cut off. Such archives can be created withtar -H posix
for instance.