On Feb 21, 2012, at 3:40 AM, Pino Toscano wrote:
> Hi,
>
> (greetings from your favourite Hurd porter)
>
> Alle lunedì 13 febbraio 2012, Tim Kientzle ha scritto:
>> So on hurd, I see a couple of interesting failures for bsdtar:
>> [...]
>
> Actually, libarch
test_copy
If you can strace or truss this (following children so we find
out what bsdtar is doing as well), that would be appreciated.
Thanks,
Tim Kientzle
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Each of these reports includes the name of the test directory, e.g.,
>> Details for failing tests: /tmp/libarchive_test.2012-02-06T23.02.12-000
Can we get the contents of those directories (which include detailed
logs for each failure, the files involved, and other details)?
Tim
On Feb 9, 201
is test to avoid
this problem on all platforms. I'll get that fix into 2.5.4.
Thank you for your patience. I'll let you know as soon as I
have a candidate fix.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Good guess, but I don't think that explains anything, since
the order in which hardlinked files get stored doesn't matter.
(There are a few tests that do detailed format verification;
those would be affected by the order in which files get stored,
but none of those depend on the ordering of readdi
self seems correct, then an strace of
bsdtar while extracting might be very illuminating.
If this doesn't shed any light, send me the contents
of /tmp/bsdtar_test_X/test_basic for one of the
failed tests. Maybe there are some other clues in there.
Cheers,
Tim Kientzle
--
To UNSUBSCRI
6 matches
Mail list logo
