From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Please set up Hydra channel for new python-build-system (was: [PATCH 00/14] Change python-build-system (fixes bug 20765)) Date: Wed, 12 Oct 2016 10:51:08 -0400 Message-ID: <20161012145108.GG18017@jasmine> References: <57EBCD98.9020407@goebel-consult.de> <87mvism34v.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> <57EC008A.4030006@crazy-compilers.com> <87bmz5ih9u.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> <87wphqesmc.fsf@gnu.org> <57F14455.8060506@crazy-compilers.com> <20161002180138.GB22791@jasmine> <57FB9688.8090500@crazy-compilers.com> <20161012142954.GC18017@jasmine> <20161012143706.GA7368@solar> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45855) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buKsP-0001qu-GG for guix-devel@gnu.org; Wed, 12 Oct 2016 10:51:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1buKsI-0004eV-Vl for guix-devel@gnu.org; Wed, 12 Oct 2016 10:51:24 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:47186) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1buKsH-0004dr-Lw for guix-devel@gnu.org; Wed, 12 Oct 2016 10:51:18 -0400 Content-Disposition: inline In-Reply-To: <20161012143706.GA7368@solar> 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" To: Andreas Enge Cc: guix-devel@gnu.org --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 12, 2016 at 04:37:06PM +0200, Andreas Enge wrote: > On Wed, Oct 12, 2016 at 10:29:54AM -0400, Leo Famulari wrote: > > I'll set up a Hydra jobset for the branch once it has been created. >=20 > Maybe it would be good to wait until core-updates is merged? Hydra is > currently busy building that. Also, there is still the wip-python branch > on hydra, maybe this could then be deleted, or commits cherry-picked? Yes, I was going to coordinate with the rest of the admins to schedule this Python rebuild. I think it should happen after this core-updates cycle. The wip-python branch is on hold until we have Python 3.5 in master. I found some significant differences in how Python 3.4 and 3.5 affect building, and I didn't want to juggle three different Python package graphs: current master, current core-updates, and wip-pytohn. The core Python packages are *extremely* tangled up in each other. Help wanted, and I do plan to tackle it after the next release, and potentially after this new build system is merged. It depends on how quickly the new build system looks ready for master. We could even restart wip-python on wip-python-build-system, since I didn't make concrete progress on wip-python, unfortunately. --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX/k3cAAoJECZG+jC6yn8IbxkP/2ryLeLRbbJ7gM0HphjDm5ex uLuUSIsN6mRGU8ol4izwQAZW8xxa4+wnpOA8Kw3UbggJ54mkNzAG2/2Gc3z8FQNa oG6eHTLl/d4/oixigfiaGSiLvgFwpvpUS2ltdNmreL6NQdIkgEx/w2ZE4FFDP2/U XoC2sJog4G9SjnA2VG7MWL8x/N+QVIrVRk/QsExpXdmMXce/ZXJkUalsOck3+X4j Ek2H2V7xCER3FqaBoFpBz+sR+zMUaxBHmzvDl7pH9twuvxzIw99+M7O0YbSQRpgn F3yCWXZeUYrRVbmN6Oq87ac5lKHd5lvdM0C9P5tFqEAdxmBjbN/lGdpqGkZo5jR0 HiCtUoSn5L0sQd3LSyNnzGouOLNUvbPPHF7/eTR6UI9NwKgqPj2eXqp/l2P6iQm3 SzBqb6qW3IY+S+QhVPbMq+tZIPPVXxwjU7zCxRmjHrk4oAc9j7Hwwd2Y/rzpbj+f 9DqHi+iSAV+EcDQ8hFRX9rZyXnJLpRDBJxfNFKF+bms1YErBGGarr9W5q6b4kR6J cMD5HKKUrKGewtIV8QIVuMlVRl/tkB7brm7uGBhZcTWh4Bo+zVsYncmXkzoHWKNm Y6mK+G7rOo1VLMPYTF0H2yjTmvtH7mlzqYOiifnfvP5MQPFaLLNyFyyf8D6sqAph 9Z8s91i5PtFJ9UWbuYMr =XXmT -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE--