From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Packaging gx (for IPFS): Need to update default Go to 1.11? Date: Wed, 7 Nov 2018 16:03:09 -0500 Message-ID: <20181107210309.GA30589@jasmine.lan> References: <878t26b0i1.fsf@ambrevar.xyz> <20181106173116.GA3232@jasmine.lan> <87k1lqyuta.fsf@ambrevar.xyz> <20181106195712.GB6749@jasmine.lan> <87a7mlz6hv.fsf@ambrevar.xyz> <87o9b0n9gr.fsf@ambrevar.xyz> <20181107182642.GA17483@jasmine.lan> <87efbwmyyz.fsf@ambrevar.xyz> <20181107204054.GA29657@jasmine.lan> <87d0rgmx59.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41801) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKVEU-0004iE-Oa for guix-devel@gnu.org; Wed, 07 Nov 2018 16:19:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKUz0-0003CU-Vk for guix-devel@gnu.org; Wed, 07 Nov 2018 16:03:31 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:51989) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gKUz0-000308-Ny for guix-devel@gnu.org; Wed, 07 Nov 2018 16:03:26 -0500 Content-Disposition: inline In-Reply-To: <87d0rgmx59.fsf@ambrevar.xyz> 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: Pierre Neidhardt Cc: Guix-devel --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 07, 2018 at 09:48:50PM +0100, Pierre Neidhardt wrote: > In my patchset, there are 2 kinds of fixes: >=20 > - Disabling tests because Go=A01.11 test policies are stricter and some l= ax code > from before does not pass anymore. > For this issue, upstream should fix their packages. As far as we are > concerned, disabling tests is enough. The go-build-system has nothing = to do > with this issue. Okay, I think you should go ahead and push these changes now, assuming the packages still build afterwards. > - Manual forwarding of compilation flags (e.g. "-tags"). This is an issu= e with > our go-build-system which cannot re-use existing "pkg" objects on Go=A0= 1.11. > Upstream code is fine. >=20 > So yes, fixing go-build-system is related to packages not building with > Go=A01.11=A0:p Okay, I see. I won't be working on this soon, if ever. I don't understand enough about how Go >=3D 1.10 builds software in order to do the work efficiently. Hopefully there is a volunteer :) --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlvjUw0ACgkQJkb6MLrK fwg13A//bQYZJvex7IQac0jYnHG0ilaU1oSzexzEDQvaV3aeFjqz5LwTLnmRl7sj ccfisQ7e3+m1HCc57G0A+I/Uztb/hSMx7+zMFsDvm+i6XrnUClJ8beSx4vqOGWpw Hlc/G3CFe5I4jNT6KR7BM/YmqLA5SmEEJ4hXK6wPepkJuLItxptcSjAF6yoHndvi BN5yTRUcmWk0HUXJ0a85p1I3n8CbY0Jzf+UXq3UyMSK0XXbnsT39C51csPi/laE2 Rl4US/50+CLNRMK3thhQC+tV+hYaJSJpKlNi0pRboZ0z2n/hK2tgHIqeJNLwlpYa xJj2o7vZxyE4aV7Z+anAxyP+qaLwg9j+QgUIl7c17Ucme3TEC8NH25o+QjBxGqMg cMbkOn1AI5XJHdXiIztePd9L+FYpcRevVRl5i8837Wetizm9th1nxZuukfkTCJWH aa94yQEFwHA1I4nmbMKry2m74Lg0YU++m9SsIfgBZ6T6M0Jgeqlq6ILIinxFZe1x pYhlZu+OFqcQPLZobjcde6wQ4a9WKDpefQUip6RFoAqeozgMDKQQRXjxn0c/1GNd 2GTF4JIxIyF/fbF86Z1xzVcOS9STh/2TSD3Di4ocOQcgBbwAxid5/JzM7Ze41oRZ kZF4ODRAaC75NIIUbzd342KltFIuq5kYjS4y5esUxn686nCMKec= =a26y -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--