Thanks. As discussed previously on pkg-multimedia-maintainers, I propose that we restrict archs for one package "supercollider-supernova". The package is optional for users (it's a non-default drop-in alternative to "supercollider-server") and there is very little upstream support for getting it working across archs. It uses some fancy coding and boost libs that I'm not familiar with, and these are what incur these build fails. I know it would be great to avoid having to special-case any archs, but I don't see where the expertise will come from to do this, and supercollider is fully-functional without that package.
Dan 2013/11/3 Niels Thykier <ni...@thykier.net>: > Package: supercollider > Version: 1:3.6.3~repack-3 > Severity: serious > > Hi, > > supercollider FTBFS on the sparc and powerpc buildds, but was built > there successfully in the past. Since sparc and powerpc are > candidates for release architectures, this failure prevents testing > migration. > > ~Niels > > Ref: https://buildd.debian.org/status/package.php?p=supercollider > > _______________________________________________ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
