Your message dated Sun, 8 Nov 2015 20:54:27 -0800
with message-id
<CAKwFPQ_fOEFS2GfuQPXnWmTRKdbvv-9VBzj7Y3Ug=ma535W=m...@mail.gmail.com>
and subject line Re: capnproto: FTBFS on armhf and armel (test seg. faults) but
built there in the past
has caused the Debian Bug report #781443,
regarding capnproto: FTBFS on armhf and armel (test seg. faults) but built
there in the past
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(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.)
--
781443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: capnproto
Version: 0.4.1-3
Severity: serious
Hi,
It seems that the current version of capnproto FTBFS on armel and
armhf due to a segmentation fault in one of the tests. This prevents
the new version of migrating to testing as it is a regression compared
to the version in testing.
Thanks,
~Niels
--- End Message ---
--- Begin Message ---
Builds on armel/armhf appear to be back to normal as of recent releases.
Closing this out. Thanks for the report!
On Sun, 29 Mar 2015 13:45:14 +0200 Niels Thykier <[email protected]> wrote:
> Source: capnproto
> Version: 0.4.1-3
> Severity: serious
>
> Hi,
>
> It seems that the current version of capnproto FTBFS on armel and
> armhf due to a segmentation fault in one of the tests. This prevents
> the new version of migrating to testing as it is a regression compared
> to the version in testing.
>
> Thanks,
> ~Niels
>
>
--- End Message ---
