Daniel Burrows dburr...@debian.org (18/01/2010):
It looks like the build succeeded on all the release
architectures, so I think I might downgrade this so that aptitude
can get into testing. (the version currently there is ancient and I
don't really want it to be held up even further by
On Tue, Jan 19, 2010 at 10:44:08AM +0100, Cyril Brulebois k...@debian.org was
heard to say:
Daniel Burrows dburr...@debian.org (18/01/2010):
It looks like the build succeeded on all the release
architectures, so I think I might downgrade this so that aptitude
can get into testing. (the
On Tue, Jan 19, 2010 at 09:23:46AM -0800, Daniel Burrows wrote:
All righty then. In that case, I'm going to disable the test cases
on kfreebsd. It looks pretty clear to me from the transcript that the
test case actually succeeded before crashing, which makes me suspect
that it's the Boost
Package: src:aptitude
Version: 0.6.1.4-1
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS on kfreebsd-i386 due to testsuite issues:
| /usr/bin/make check-TESTS
| make[2]: Entering directory
Weird thing is: I get the same failure, but it doesn't kill the build.
It should. So by my count that's two bugs here :-/.
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Ah, I got fooled by some garbage printed by the cppunit test. The
actual problem is the double-free in the Boost tester. D'oh.
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
OK, I can't see any sign of a double-free in either valgrind or
libefence, which are usually pretty good about catching this sort of
thing. Can you run something similar on FreeBSD and see what it says?
Thanks,
Daniel
--
To UNSUBSCRIBE, email to
Daniel Burrows dburr...@debian.org (18/01/2010):
OK, I can't see any sign of a double-free in either valgrind or
libefence, which are usually pretty good about catching this sort of
thing. Can you run something similar on FreeBSD and see what it says?
Sorry for the delay… (we just started
Cyril Brulebois k...@debian.org (19/01/2010):
I've asked some folks on #-kbsd to keep an eye on this bug in case
they have some time to track it down. Hopefully you'll hear from one
of us soonish.
Hrm, this is strange.
Given my previous observations about --debug, I tried adding a cout
call
On Tue, Jan 19, 2010 at 03:32:36AM +0100, Cyril Brulebois k...@debian.org was
heard to say:
Only keeping the #include line is sufficient, I can't reproduce this
issue double free issue.
Weird.
It looks like the build succeeded on all the release architectures, so
I think I might downgrade
10 matches
Mail list logo
