From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Tom=C3=A1=C5=A1_?= =?UTF-8?Q?=C4=8Cech?= Subject: bug#39976: next browser fails to build Date: Sat, 7 Mar 2020 17:39:45 +0100 Message-ID: <20200307163945.GB1773@doom> References: <20200307152831.GA1773@doom> <87d09o87oz.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mojUlQ0s9EVzWg2t" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46387) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAcXY-0000vI-5V for bug-guix@gnu.org; Sat, 07 Mar 2020 11:43:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAcXX-0008Kc-8n for bug-guix@gnu.org; Sat, 07 Mar 2020 11:43:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:41486) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAcXX-0008Jl-5b for bug-guix@gnu.org; Sat, 07 Mar 2020 11:43:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAcXX-0001AD-4f for bug-guix@gnu.org; Sat, 07 Mar 2020 11:43:03 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87d09o87oz.fsf@ambrevar.xyz> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Pierre Neidhardt Cc: 39976-done@debbugs.gnu.org --mojUlQ0s9EVzWg2t Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! On Sat, Mar 07, 2020 at 05:13:00PM +0100, Pierre Neidhardt wrote: >Hi! > >Glad to see you are interested in Next! :) > >Next 1.5.0 should work rather well on Guix. > >However the SBCL 2.0.2 update broke it. But no worries, I've just >pushed a fix so you should able to install Next after a `guix pull'. > >I'm hard at work with Next 2.0 and it should fix some long standing >issues that are still in Next 1.5.0. Thanks for swift response and reaction. I can confirm that new pull fixes the issue for me. >Stay tuned! I will, good luck with 2.0! Best regards, Tom=C3=A1=C5=A1 =C4=8Cech PS: I used bug-tracker e-mail in initial e-mail but you got the e-mail without assigned bug. So your response probably opened new one - please, be so kind and close it. --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEDOrssfr9jDQthC2PSiPjT6AzQ20FAl5jzlEACgkQSiPjT6Az Q21V6g//WtUeL9Z8Evvaym/GluIdwzzzTC0fdyS+LARg65nkP6xWyyI9LtJAj2d3 QkZMZ/fhH5un6ZQdlQECpbcD3JoVx4pUU6EGAcL78OeIuPq4MYCHy8R7xS/S/1DW lRHVYhkHY6tpovAYqqbgV/UVBLqj2y1OoYT0rOTonQD/zuCgXEG/6I3N8uZZ3wOC QYX1mjgCIfQ6ODJBadfQ/y+MAuG02PAZTRhP7zk6pbJrqjPCODS/GKWnBSUDsYkH IVYG9CXV7sa0Gg/n3XvGcCdkqPxbfHdVOXJyVCq+s+0FuergmZKUALvEEbpSCrPv KiCDmjQUE2dF2aWGW2UdoPg8J3UlE/9wv6U3yKf84cVE7sy/61N75xZQx7GYL8Zq VQJay/ki2EQT52J7rPh54D01PO5zkNU7/st54DpbuaqQ+J2A7zQbdzLqqrRYII7T avoKKi14HB1LFGxMk2taQIH12LFWMeeVvt/PpLMRfXtYGtZfoSwsMdx6qYR2hn9T BzqmIT5Q/uPpmZNTqtDFx4651X4+bNps6UFXY5FT6Lc/URzhUgyuOpIks/htvgEA +qLOBlRh+6owS/Z1oa9WXBCMVZSUpu0dPcUr/qCreEyI+/WlMhpZYQvBoly8kUeV bBTkFG8cS7s0786Q3Qw06yN9rOv8QKhgTIau5U0nON/1S2ZAKgE= =LFex -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t--