From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Qt-5 in core-updates Date: Mon, 25 Jan 2016 19:04:36 +0100 Message-ID: <20160125180436.GA7683@debian.eduroam.u-bordeaux.fr> References: <20160124191925.GA4264@debian> <87twm2ctfq.fsf@member.fsf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56673) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNlVN-0000mv-SZ for guix-devel@gnu.org; Mon, 25 Jan 2016 13:04:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNlVI-0006Gp-Sy for guix-devel@gnu.org; Mon, 25 Jan 2016 13:04:45 -0500 Received: from mailrelay6.public.one.com ([91.198.169.200]:27556) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNlVI-0006GW-Hg for guix-devel@gnu.org; Mon, 25 Jan 2016 13:04:40 -0500 Content-Disposition: inline In-Reply-To: <87twm2ctfq.fsf@member.fsf.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: =?utf-8?B?5a6L5paH5q2m?= Cc: guix-devel@gnu.org Thanks, 宋文武, for this thorough research! On Mon, Jan 25, 2016 at 09:57:13AM +0800, 宋文武 wrote: > - Patch our python-2.7.x like Ubuntu does. > To me, this sounds like the cleanest solution, but probably not in this core- updates run, which has taken quite some time already. > - Patch the build phases of qt and webkitgtk to pre-generate *.pyc > files before the actually building. This I would not know how to do, and we would need to do it for webkitgtk also (of which we have three variants! so an independent question: can this maybe be reduced? it seems to depend on gnucash). > - Restart the builds on hydra, hope it will pass. This one I already tried, and I also built qt-5 once on my machine. Áll three builds failed consistently. So something has apparently changed on core-updates compared to master that triggers this failure. > Or disable parallel build completely. That looks like the best short-term solution. I will try it locally and push it to core-updates if it works, with "FIXME" remarks for after this core-updates cycle. Andreas