Bug#728573: supercollider: FTBFS on sparc and ppc but built there in the past

Felipe Sateler fsateler at debian.org
Mon Nov 25 13:30:15 UTC 2013


On Sun, Nov 24, 2013 at 9:48 AM, Dan S <danstowell+debmm at gmail.com> wrote:
> 2013/11/6 Felipe Sateler <fsateler at debian.org>:
>> On Sun, Nov 3, 2013 at 7:44 AM, Dan S <danstowell+debmm at gmail.com> wrote:
>>>
>>> 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.
>>
>> I thought sc used the problematic boost libs elsewhere so this was not
>> really a workable solution...
>
> Hi all - just tested this on sparc/ppc porterboxes and the proposed
> fix works. I've pushed the fix to git.debian.org - please could I
> request a new upload, so that it's possible for the supercollider
> packages to go eventually to testing?

Looks like it got built everywhere :)

https://buildd.debian.org/status/package.php?p=supercollider


-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list