[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#576857: marked as done (gjdoc bus errors on kfreebsb-amd64)

Your message dated Thu, 08 Apr 2010 20:55:05 +0200
with message-id <1270752905.3113.10.camel@localhost.localdomain>
and subject line Re: gjdoc bus errors on kfreebsb-amd64
has caused the Debian Bug report #576857,
regarding gjdoc bus errors on kfreebsb-amd64
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 owner@bugs.debian.org
immediately.)


-- 
576857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576857
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcj-4.4-jdk
Version: 4.4.3-5
Severity: serious

/usr/lib/jvm/default-java/bin/javadoc exits due to a bus error causing
FTBFS failures on freebsd-amd64.

The default javadoc on freebsd-amd64 is /usr/bin/gjdoc-4.4.

Here are two examples of FTBFS javadoc generation on freebsd-amd64:

https://buildd.debian.org/fetch.cgi?pkg=brltty&arch=kfreebsd-amd64&ver=4.1-5&stamp=1269472138&file=log&as=raw

https://buildd.debian.org/fetch.cgi?pkg=voms&arch=kfreebsd-amd64&ver=1.9.16.1-2&stamp=1270661799&file=log&as=raw

Attachment: signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel


--- End Message ---
--- Begin Message --- 
tor 2010-04-08 klockan 20:40 +0200 skrev Mattias Ellert:
> After receiving your message, I asked for a give-back of the two
> packages. This resulted in brltty building fine, but voms failing again
> with the same bus error.
> 
> Looking through the logs all the failures with bus errors have happened
> on the build machine called "fasch", while the successful brltty build
> was done on the build machine called "fano".
> 
> I therefore suspect that this problem is related to the build machine
> called "fasch".
> 
> 	Mattias

A third attempt to build voms succeeded, this time on "fano". So this is
even more indication that the problem is related to "fasch".

	Mattias

Attachment: smime.p7s
Description: S/MIME cryptographic signature


--- End Message ---
Reply to: