Hi again,
Nice bug descriptions. :)
Christopher L Conway wrote:
> What should be the disposition of this bug?
I guess it should be merged with one of the two offshoots.
Happy debugging,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscr
I've requested removal of the failing binaries here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576333
The regression failures appear to fall into two classes. I've cloned a
bug for the std::bad_alloc error here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576334
The JVM crash
Hi Chris,
Christopher L Conway wrote:
> the problem architectures are not directly supported by
> upstream and I don't have access to testing machines for these
> architectures, I'm not sure what the correct resolution is. Should I
> remove these architectures in debian/control?
I’d suggest some
Kibi,
Thanks for reporting this. I've already file a bug upstream for these
errors. As the problem architectures are not directly supported by
upstream and I don't have access to testing machines for these
architectures, I'm not sure what the correct resolution is. Should I
remove these architectu
Source: cvc3
Version: 2.2-11
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS in various ways, on various archs:
armel:
| Running API test, regress level = 0
|
| test(): {
| Lambda application: (LAMBDA (x: INT): x)(1)
| Simplified: 1
|
| }
| test1(): {
| Query: TRUE
| Valid
|
| Q
5 matches
Mail list logo
