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. But I've been quite
busy lately and hadn't got the chance to do it yet (also being it in unstable
only during the freeze it does not have a very high priority right now).

> 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. I think it can be set as fixed by icu/4.8.1.1-8.

Cheers

-- 
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'

Attachment: signature.asc
Description: Digital signature

Reply via email to