[LHF] making t5000 "tar xf" tests more lenient

2012-12-24 Thread Junio C Hamano
I've been running testsuite on a few platforms that are unfamiliar to me, and was bitten by BSD implementation of tar that do not grok the extended pax headers. I've already fixed one in t9502 [*1*] where we produce a tarball with "git archive" and then try to validate it with the platform impleme

Re: [LHF] making t5000 "tar xf" tests more lenient

2013-01-05 Thread René Scharfe
Am 24.12.2012 21:49, schrieb Junio C Hamano: > I've been running testsuite on a few platforms that are unfamiliar > to me, and was bitten by BSD implementation of tar that do not grok > the extended pax headers. I've already fixed one in t9502 [*1*] > where we produce a tarball with "git archive"

Re: [LHF] making t5000 "tar xf" tests more lenient

2013-01-05 Thread Junio C Hamano
René Scharfe writes: > Anyway, I don't think the pax headers are to blame here. The patch below > fixes the tar failures for me, but I'm not sure why. There must be > something special about some (not all!) directory entries with trailing > slashes after directory names. > > Several ZIP tests s

Re: [LHF] making t5000 "tar xf" tests more lenient

2013-01-05 Thread Junio C Hamano
René Scharfe writes: > Anyway, I don't think the pax headers are to blame here. Hmph, I am reasonably sure I saw a test that created an archive from a commit (hence with pax header), asked platform tar to either list the contents or actually extracted to the filesystem, and tried to ensure nothi

Re: [LHF] making t5000 "tar xf" tests more lenient

2013-01-05 Thread René Scharfe
Am 05.01.2013 21:11, schrieb Junio C Hamano: René Scharfe writes: Anyway, I don't think the pax headers are to blame here. Hmph, I am reasonably sure I saw a test that created an archive from a commit (hence with pax header), asked platform tar to either list the contents or actually extract