From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-lisp+bounces-249-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D808613827E for <garchives@archives.gentoo.org>; Tue, 10 Dec 2013 09:25:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 686AFE0B58; Tue, 10 Dec 2013 09:25:18 +0000 (UTC) Received: from nimiux.org (nimiux.org [176.31.114.133]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BC3A2E0B58 for <gentoo-lisp@lists.gentoo.org>; Tue, 10 Dec 2013 09:25:17 +0000 (UTC) Received: from bolita.nimiux.org (unknown [89.7.128.183]) by nimiux.org (Postfix) with ESMTPSA id 7BC9C20051 for <gentoo-lisp@lists.gentoo.org>; Tue, 10 Dec 2013 10:25:16 +0100 (CET) Date: Tue, 10 Dec 2013 10:26:12 +0100 From: Chema Alonso <nimiux@gentoo.org> To: gentoo-lisp@lists.gentoo.org Subject: Re: [gentoo-lisp] Stabilization of last versions of sbcl and asdf on amd64 Message-ID: <20131210092612.GA7274@filladhoo> Mail-Followup-To: gentoo-lisp@lists.gentoo.org References: <20131209153357.GA29832@filladhoo> <alpine.LFD.2.03.1312100159580.15577@star.inp.nsk.su> Precedence: bulk List-Post: <mailto:gentoo-lisp@lists.gentoo.org> List-Help: <mailto:gentoo-lisp+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-lisp+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-lisp+subscribe@lists.gentoo.org> List-Id: Gentoo Lisp mail <gentoo-lisp.gentoo.org> X-BeenThere: gentoo-lisp@lists.gentoo.org Reply-To: gentoo-lisp@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <alpine.LFD.2.03.1312100159580.15577@star.inp.nsk.su> Organization: gentoo.org User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: cc6309dd-84ef-4e8a-bfc8-2f257caa536a X-Archives-Hash: a70fa0670d11e1a6e2d43b2bd2548eaf --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 10, 2013 at 02:11:05AM +0700, grozin@gentoo.org wrote: > On Mon, 9 Dec 2013, Chema Alonso wrote: > > BTW sbcl-1.1.14 is out there, I've tested it on amd64 using the ebuild > > for 1.1.12 and it builds and runs fine. Is it ok to push it to the tree? > Thanks, I've committed it. >=20 > > WRT bugs 485630 [1] and 485632 [2], I've tested the last vesions of > > sbcl and asdf, particularly: > > > > dev-lisp/sbcl-1.1.12 > > dev-lisp/asdf-3.0.2.4 > > dev-lisp/uiop-3.0.2.4 > > > > They build and run with no problesms on amd64. All tests pass. > > > > As an amd64 arch tester is ok for me to stabilize them. > > > > Any comments/problems? > I think it's OK to stabilize it on amd64. Done >=20 > The bug #486552 is a major problem: nobody can compile any version of sbc= l=20 > on x86, starting from some moment between May and August 2013, due to som= e=20 > change in something completely unrelated to sbcl. So, on x86 it definitel= y=20 > should not be stabilized. >=20 > By the way, the original reporter of this bug had this problem on an amd6= 4=20 > system; only after he fully updated it to ~amd64, the problem had=20 > disappeared. I suppose you have tested on a stable amd64, right? So, it= =20 > seems that the problem disappeared, and stabilizing on amd64 is OK. >=20 I tested it on an stable amd64 system, no problems found apart from some 'cosmetic' warnings found by repoman: ebuild.minorsyn 12 dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on l= ine: 50 dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on l= ine: 62 dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on l= ine: 51 dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on l= ine: 64 dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line= : 57 dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line= : 70 dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line= : 57 dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line= : 70 dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line= : 57 dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line= : 70 dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line= : 56 dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line= : 69 These are easy to fix though =3D) Will you take care of them? Thanks. Regards. > Andrey >=20 --=20 --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJSpt40AAoJEA2sAkrWKOU2zmsH/3cPoDEyFmH/TwRollSDxjjI Uw2fQne4FpDqqaN6Ae46amYGjEBU1ipamAQ2ViclhMm9ma0QkTOivDd4V5z0D7dw zkX08uatM4EmQOHDV75z4d7d+N1tpS6C8nk/O9TdNCYeIzf79OSO/Nw8TYb5HEKj qdAe0z77bpBgJph3vNIXMSjyMkg00Ey7ZBaTxvblIoe44t2lbwwsPolSxn6HqOOE aoammxNa8W6/xolmbo+Kk+XRdhwg/HacoZlJsRKv0q0W9awrTqBfGMJkNUzEJYcU JUhrcFxERvwcgi5Ey/xXqW3mQ9kLSAJzcxxsIxtOyQrIZYQ41fBNmfZI5g+Iwhk= =fRpD -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--