Hello As mentioned in #636944, there's a mismatch between parrot's declated build-dependencies and what was actually used to build parrot. In i386 case, parrot was build with libffi. In all other arch, parrot is built without libffi.
This triggers a FTBS for rakudo on i386 because parrot looks for libffi include files. This binNMU is a stopgap solution to resolve rakudo's FTBS. We need to discuss with upstream parrot to find a long term solution. Theoritically, the following commands should trigger a rakudo rebuild once parrot has been binNMU'ed. Hope I'm right nmu parrot_3.6.0-1 . i386 . -m 'rebuild to exclude libffi (fix config mismatch between arches and rakudo FTBS)' dw rakudo_0.1~2011.07-1 . i386 . -m '(>= parrot_3.6.0-1+b1)' Thanks Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/
signature.asc
Description: This is a digitally signed message part.
