@jgoerzen: "Hi,
I have several "excuses" pages that resemble this one:
<url>
This says that darcs-buildpackage has new bugs, and references #410838.  But 
#410838 is resolved in unstable and has been for ages  since February.  
Why is that still a reason to keep it out of testing?
Also, what's up with mips and mipsel?  Many of my packages are kept out of 
testing because they're out of date on those archs.
 John
To UNSUBSCRIBE, email to <email_address>
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @dato: "* John Goerzen [Wed, 01 Aug 2007 10:56:08 -0500]:
<quote>
Without being a bugscan/britney hacker, I think what's happening it's
that #410838 is being counted precisely because the fixed version is not
built on mips. Once it's built there, the package will no longer be
considered buggy.
Many build failures due to uninstallable stuff has been queuing up
lately. I've gone over a lot of them in the past days, but darcs-buildpackage
did not show in my list of otherwise-ready packages, precisely because
it was not built on mipsel. Heh.
I'll ask for a retry.
Cheers,
Adeodato Simó                                     lawrence40@example.org
Debian Developer                                  lawrence40@example.org
                            Listening to: Radio Futura - Condena de amor
To UNSUBSCRIBE, email to <email_address>
with a subject of "unsubscribe". Trouble? Contact <email_address>"
    @jgoerzen: "<quote>
Yeah, I noticed that part.  Actually it appears that GHC is generating 
binaries that are crashing with a bus error on that platform, which is the 
root cause.  I just wondered why the bugs were showing up, because they 
shouldn't be.
To UNSUBSCRIBE, email to <email_address>
with a subject of "unsubscribe". Trouble? Contact <email_address>"
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "linux.debian.devel.20141028.mbox"}', 'file': 'data/output/usenet-linux.debian.parquet'}