| 1 |
On Tue, 2018-01-02 at 09:18 -0800, Jigme Datse Yli-RAsku wrote: |
| 2 |
> I'm not sure where best to address this, so for now I am starting |
| 3 |
> here. |
| 4 |
> I'd like to have this addressed, and be able to emerge it without |
| 5 |
> disabling "multilib-strict" as it seems that this has been enabled |
| 6 |
> because these packages are going to end up hard failing before too |
| 7 |
> long. |
| 8 |
> |
| 9 |
> Is there a good way to end up reporting these kinds of things? I |
| 10 |
> really |
| 11 |
> wish this (and other packages which might have this problem) |
| 12 |
> fixed. If |
| 13 |
> this isn't the right place to put this, could someone tell me where, |
| 14 |
> and |
| 15 |
> if I need other information? |
| 16 |
|
| 17 |
File a bug on bugzilla, but in this case, there exists one already: |
| 18 |
|
| 19 |
https://bugs.gentoo.org/628362 |
| 20 |
|
| 21 |
But I see supercollider does not currently have a Gentoo maintainer, so |
| 22 |
you might want to consider proxy-maintaining it or something. |
| 23 |
|
| 24 |
It has a fix suggestion on the bug already, no idea if that's the best |
| 25 |
approach though. |
Archives