Your message dated Thu, 3 Mar 2011 14:24:48 +0100
with message-id <[email protected]>
and subject line armel builds now fine
has caused the Debian Bug report #580975,
regarding jack-audio-connection-kit sometimes FTBFS on some armel buildds with
illegal instruction error
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.)
--
580975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580975
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: jack-audio-connection kit
x-debbugs-cc: [email protected]
x-debbugs-cc: [email protected]
note: i'm not sure what severity this deserves. If it's a really a bug
in the package it's probablly rc OTOH it could just be something screwy
with the buildd chroots and not really be a bug in the package at all. I
am therefore leaving the judgement call on severity up to the maintainer.
Attempts to build jack-audio-connection-kit on all6500-2 and muscat seem
to be failing with an illegal instruction error.
https://buildd.debian.org/fetch.cgi?&pkg=jack-audio-connection-kit&ver=1.9.5~dfsg-9&arch=armel&stamp=1273219333&file=log
https://buildd.debian.org/fetch.cgi?&pkg=jack-audio-connection-kit&ver=1.9.5~dfsg-9&arch=armel&stamp=1273213323&file=log
https://buildd.debian.org/fetch.cgi?&pkg=jack-audio-connection-kit&ver=1.9.5~dfsg-13&arch=armel&stamp=1273406338&file=log
https://buildd.debian.org/fetch.cgi?&pkg=jack-audio-connection-kit&ver=1.9.5~dfsg-13&arch=armel&stamp=1273430446&file=log
https://buildd.debian.org/fetch.cgi?&pkg=jack-audio-connection-kit&ver=1.9.5~dfsg-13&arch=armel&stamp=1273432641&file=log
Other armel buildds and my qemu armel system seem to be building it
successfully (or for older versions running into 580618).
Can anyone reproduce this problem outside a buildd environment? Does
anyone have any ideas as to what may be the cause?
--- End Message ---
--- Begin Message ---
Hi!
This bug seemed to be a temporary hiccup on some armel buildds.
According to
https://buildd.debian.org/fetch.cgi?pkg=jackd2;ver=1.9.6~dfsg.1-5;arch=armel;stamp=1296327641
the package builds correctly "now".
Cheers
--
mail: [email protected] http://adi.thur.de PGP/GPG: key via keyserver
--- End Message ---
