From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 12B0C138206 for ; Tue, 2 Jan 2018 17:52:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0936EE0891; Tue, 2 Jan 2018 17:52:26 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AB22CE0871 for ; Tue, 2 Jan 2018 17:52:25 +0000 (UTC) Received: from [192.168.2.51] (85.253.86.194.cable.starman.ee [85.253.86.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: leio) by smtp.gentoo.org (Postfix) with ESMTPSA id E7871335C09 for ; Tue, 2 Jan 2018 17:52:22 +0000 (UTC) Message-ID: <1514915539.17094.3.camel@gentoo.org> Subject: Re: [gentoo-user] Emerging media-sound/supercollider fails with"multilib-strict check failed!" From: Mart Raudsepp To: gentoo-user@lists.gentoo.org Date: Tue, 02 Jan 2018 19:52:19 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9c99023c-199f-4630-9b4d-9002ec31e6f9 X-Archives-Hash: 5c65f57aa5f5321785fa108d6f4dc0b5 On Tue, 2018-01-02 at 09:18 -0800, Jigme Datse Yli-RAsku wrote: > I'm not sure where best to address this, so for now I am starting > here. > I'd like to have this addressed, and be able to emerge it without > disabling "multilib-strict" as it seems that this has been enabled > because these packages are going to end up hard failing before too > long. > > Is there a good way to end up reporting these kinds of things?  I > really > wish this (and other packages which might have this problem) > fixed.  If > this isn't the right place to put this, could someone tell me where, > and > if I need other information? File a bug on bugzilla, but in this case, there exists one already: https://bugs.gentoo.org/628362 But I see supercollider does not currently have a Gentoo maintainer, so you might want to consider proxy-maintaining it or something. It has a fix suggestion on the bug already, no idea if that's the best approach though.