Thx for this help! Did you test on the very same buildd/porterbox
which reports the issue: hasse.debian.org; or any other armhf/mipsel
box?
I don't have access to the autobuilders, on which logins are restricted
to their actual maintainers. Rather, my test builds were on
harris.debian.org
Thx for this help! Did you test on the very same buildd/porterbox
which reports the issue: hasse.debian.org; or any other armhf/mipsel
box?
I don't have access to the autobuilders, on which logins are restricted
to their actual maintainers. Rather, my test builds were on
harris.debian.org
Hi Aaron!
How can I best simulate the environment at the buildd box? Is there a
chance to obtain a core dump from the buildd box, alternatively?
I'm not aware of a way to get core dumps off of autobuilders, though
perhaps if you asked their maintainers nicely, they might be able to
help you
Builds of nsf on Linux architectures failed with test suite errors, of
two types. (There was also a kFreeBSD failure, which I'll report
separately.)
On armhf and mipsel, the linearization test segfaults when done:
We will certainly look at these a.s.a.p.
I tried to reproduce the
Hi Aaron!
Thx for reporting, I had already noticed the failing builds.
Builds of nsf on Linux architectures failed with test suite errors, of
two types. (There was also a kFreeBSD failure, which I'll report
separately.)
On armhf and mipsel, the linearization test segfaults when done:
We
On the remaining Linux architectures, the http test times out, perhaps
due to idiosyncracies of buildd network configuration:
!!!::req1 (2): Connection refused by host 'localhost' port '8086'
error flushing sock949f8a8: socket is not connected!!!
xocomm/test.001: incorrect result for
Sven,
I refrain from uploading that right now, in case you can come up with
something more appropriate.
Sven,
I refrain from uploading that right now, in case you can come up with
something more appropriate.
I was desperately looking for the quirk in the source package, only to
find out in
Sven,
Thx for taking of uploading!
Uploaded but it FTBFS.
Yes, there are several .o and .so files left over by the build system.
Until that's fixed I could offer a very quick and ugly workaround (attached).
I refrain from uploading that right now, in case you can come up with
something
Alex, Moritz,
Moritz is actually right, your --with-expat=sys is a mere placebo
treatment. this flag has just been added to the xotcl build system in
response to the debian security bulletins. the upcoming 1.6.6 release
provides support for shared expat. i hope that the upstream release will
9 matches
Mail list logo
