And the bad thing about it is that shogun would compile on all these archs if dependencies would become available (as they were) and clang would work on powerpc.
The only other option I see is to split up shogun into several independent source package - one for each of its interfaces and to build it separately for any of those. That however is a lot of work I cannot currently do. Soeren On Mon, 2012-04-23 at 17:39 -0400, Yaroslav Halchenko wrote: > yes -- situation is quite ugly but the problem is that ATM > shogun-python-modular is not installable even on amd64 and i386 where it > is buildable... > > anyways -- I guess I will just drop shogun from build-depends for > python-mvpa atm (used only for unittesting and shouldn't fail if shogun > is NA but then it will not be testing this particular fix :-/ ) so > python-mvpa itself would not be hurt by problems with shogun. > > > On Mon, 23 Apr 2012, Julien Cristau wrote: > > > uninstallable on sid (#669005) which would preclude closing this > > > issue -- I guess I will just request a binNMU first on behalf of Soeren. > > > I don't think a binNMU makes sense, looking at the state of > > https://buildd.debian.org/status/package.php?p=shogun > -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962
signature.asc
Description: This is a digitally signed message part
