Hi,
(triaging RC bugs)
Julien Cristau wrote (29 Sep 2012 20:30:25 GMT) :
On Sat, Sep 29, 2012 at 13:22:35 -0700, Jonathan Duke Leto wrote:
Is this an intermittent occurrence, or can you reproduce this reliably?
I have no idea, I'm just the messenger here. Talk to
i...@buildd.debian.org
On dom, nov 11, 2012 at 11:50:26 +0100, intrigeri wrote:
Did this happen?
I don't think so. Though, given the new failures in 4.6.0-1, I wanted to try to
get some more information about it from the porterbox and try what happens with
the new upstream version before contacting the ia64 people.
Hi,
Alessandro Ghedini wrote (11 Nov 2012 12:21:21 GMT) :
As far as can see, parrot is currently RC-buggy in testing (#675895)
AFAICT that bug shouldn't apply anymore since icu has been fixed in
4.8.1.1-8 to not pass hardening flags. In fact I cannot reproduce
the FTBFS on a wheezy chroot.
On 09/29, Jonathan Duke Leto wrote:
Howdy Julien,
Thanks for the bug report! We have seen something like this from the
debian build machines before, but previous reporters could not
reproduce it when compiling by hand. It seems to only happen on ia64
and looks like some kind of memory
Source: parrot
Version: 4.3.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
See the build log at
https://buildd.debian.org/status/fetch.php?pkg=parrotarch=ia64ver=4.3.0-2stamp=1342539567
./parrot-nqp --target=pir
Howdy Julien,
Thanks for the bug report! We have seen something like this from the
debian build machines before, but previous reporters could not
reproduce it when compiling by hand. It seems to only happen on ia64
and looks like some kind of memory corruption.
Is this an intermittent
On Sat, Sep 29, 2012 at 13:22:35 -0700, Jonathan Duke Leto wrote:
Howdy Julien,
Thanks for the bug report! We have seen something like this from the
debian build machines before, but previous reporters could not
reproduce it when compiling by hand. It seems to only happen on ia64
and looks
7 matches
Mail list logo
