public inbox for gentoo-lisp@lists.gentoo.org
 help / color / mirror / Atom feed
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
Date: Tue, 10 Dec 2013 10:26:12 +0100	[thread overview]
Message-ID: <20131210092612.GA7274@filladhoo> (raw)
In-Reply-To: <alpine.LFD.2.03.1312100159580.15577@star.inp.nsk.su>

[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]

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.
> 
> > 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

> 
> The bug #486552 is a major problem: nobody can compile any version of sbcl 
> on x86, starting from some moment between May and August 2013, due to some 
> change in something completely unrelated to sbcl. So, on x86 it definitely 
> should not be stabilized.
> 
> By the way, the original reporter of this bug had this problem on an amd64 
> system; only after he fully updated it to ~amd64, the problem had 
> disappeared. I suppose you have tested on a stable amd64, right? So, it 
> seems that the problem disappeared, and stabilizing on amd64 is OK.
> 

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 line: 50
   dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 62
   dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 51
   dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 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 =)

Will you take care of them?

Thanks.

Regards.

> Andrey
> 

-- 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-12-10  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 15:33 [gentoo-lisp] Stabilization of last versions of sbcl and asdf on amd64 Chema Alonso
2013-12-09 19:11 ` grozin
2013-12-10  9:26   ` Chema Alonso [this message]
2013-12-10  9:54     ` Ulrich Mueller
2013-12-10 10:23     ` grozin
2013-12-11 14:02       ` Chema Alonso
2013-12-11 14:21         ` Ulrich Mueller
2013-12-11 20:33         ` grozin
2013-12-11 20:05   ` Chema Alonso
2013-12-11 20:31     ` grozin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131210092612.GA7274@filladhoo \
    --to=nimiux@gentoo.org \
    --cc=gentoo-lisp@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox