Your message dated Wed, 09 Apr 2008 09:40:07 -0700
with message-id <[EMAIL PROTECTED]>
has caused the report #474400,
regarding libarchive: FAIL: bsdtar_test
to be marked as having been forwarded to the upstream software
author(s) John Goerzen <[EMAIL PROTECTED]>
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
474400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474400
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
A very strange failure indeed. Thanks for forwarding the
contents of the test directory. At a minimum, I hope to
have additional tests soon to help narrow the failure.
I'll be in touch...
John Goerzen wrote:
Hi Tim,
At Debian, we're seeing some odd behavior on one of the libarchive tests on
our build daemon network. An example of the output from such a failure is
here:
http://buildd.debian.org/fetch.cgi?pkg=libarchive;ver=2.4.17-1;arch=amd64;stamp=1207234654
Now here's the weird part. I can't duplicate this anywhere. The above
failure was on amd64, but on another amd64 machine that I have access to, I
can't duplicate the problem.
I've asked Kurt Roecx, who works with the build daemons, some questions about
the build. His answers are in the forwarded message below. He's also
included tarballs of the build directory and test directory in case that is
of interest to you.
I'm happy to try to figure out what is causing this test to fail, but I'm not
completely sure what would be most useful at this point.
This is 2.4.17.
Thanks again for your work in libarchive.
-- John
--- End Message ---
