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.

Author Jonathan Hsu
Recipients Jonathan Hsu, Manjusaka, dtamuc, python-dev
Date 2020-03-27.01:49:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585273768.41.0.47836927567.issue40049@roundup.psfhosted.org>
In-reply-to
Content
This is caused when tarfile tries to write a symlink that already exists. Any exceptions to os.symlink() as handled as if the platform doesn't support symlinks, so it scans the entire tar to try and find the linked files. When it resumes extraction, it needs to do a negative seek to pick up where it left off, which causes the exception.

I've reproduced the error on both Windows 10 and Ubuntu running on WSL. Python 2.7 handled this situation by checking if the symlink exists, but it looks like the entire tarfile library was replaced with an alternate implementation that doesn't check if the symlink exists. I've created a pull request to address this issue.
History
Date User Action Args
2020-03-27 01:49:28Jonathan Hsusetrecipients: + Jonathan Hsu, python-dev, Manjusaka, dtamuc
2020-03-27 01:49:28Jonathan Hsusetmessageid: <1585273768.41.0.47836927567.issue40049@roundup.psfhosted.org>
2020-03-27 01:49:28Jonathan Hsulinkissue40049 messages
2020-03-27 01:49:28Jonathan Hsucreate