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 lars.gustaebel
Recipients lars.gustaebel, mkv
Date 2009-05-23.12:03:18
SpamBayes Score 3.674409e-08
Marked as misclassified No
Message-id <1243080200.96.0.764129930824.issue6054@psf.upfronthosting.co.za>
In-reply-to
Content
Apparently, the .deb file format is not explicit about that, but it
seems to be common practice to have all files prefixed with './'.

normpath is used all over tarfile, crucial are the occurrences in
TarFile.add() and TarInfo.get_info(). As you're using a unix-like system
the easiest workaround is to replace the module level tarfile.normpath
function with a no-op.

The original assumption for using normpath on all pathnames was to keep
the names in an archive clean and in their canonical form. Most
occurrences of normpath date back to the 2003 original version (cp.
r30613) and have never been touched.

But, I found nothing in POSIX about normalizing pathnames. GNU tar and
star both strip different leading path components like "./" and "../"
from pathnames, but they both don't remove "./" components from inside a
pathname, for example. This means that the usage of normpath seems more
or less unnecessary in tarfile.

I will create a patch that addresses these issues.

Thanks for your report.
History
Date User Action Args
2009-05-23 12:03:21lars.gustaebelsetrecipients: + lars.gustaebel, mkv
2009-05-23 12:03:20lars.gustaebelsetmessageid: <1243080200.96.0.764129930824.issue6054@psf.upfronthosting.co.za>
2009-05-23 12:03:19lars.gustaebellinkissue6054 messages
2009-05-23 12:03:18lars.gustaebelcreate