Hi Goswin, Goswin von Brederlow ([EMAIL PROTECTED]) wrote on 09:21:50AM 05/09/04: > Why not fix it yourself? Since you seem to use clisp I guess you are > familiar with it?
I actually did try to fix the bug in clisp but I didn't succeed at it because I didn't know enough about MIPS assembly in order to follow through on it. My requests on the debian-mips mailing lists all went unanswered[1]. > Do you think it wise to exclude packages from an arch just because it > has some bug? If the maintainer can't be bothered to fix a bug the > package should not enter testing. Excluding an arch just works around > semi orphaned packages. Just in case you didn't get it, the problem is not even in *my* package. The clisp package at some point built the FFI module for mips, which let my mcvs package be built and propagated into testing. Then the clisp maintainer turned off building the FFI module for certain architectures (including mips), making it impossible for mcvs to build successfully for those architectures from that point on. I agree with you that the *clisp* package w/o FFI on some architectures shouldn't have made it into testing but it did, and that's how things stand now. - robin [1] http://lists.debian.org/debian-mips/2004/05/msg00141.html http://lists.debian.org/debian-mips/2004/06/msg00035.html
