| 1 |
On Tue, Dec 10, 2013 at 02:11:05AM +0700, grozin@g.o wrote: |
| 2 |
> On Mon, 9 Dec 2013, Chema Alonso wrote: |
| 3 |
> > BTW sbcl-1.1.14 is out there, I've tested it on amd64 using the ebuild |
| 4 |
> > for 1.1.12 and it builds and runs fine. Is it ok to push it to the tree? |
| 5 |
> Thanks, I've committed it. |
| 6 |
> |
| 7 |
> > WRT bugs 485630 [1] and 485632 [2], I've tested the last vesions of |
| 8 |
> > sbcl and asdf, particularly: |
| 9 |
> > |
| 10 |
> > dev-lisp/sbcl-1.1.12 |
| 11 |
> > dev-lisp/asdf-3.0.2.4 |
| 12 |
> > dev-lisp/uiop-3.0.2.4 |
| 13 |
> > |
| 14 |
> > They build and run with no problesms on amd64. All tests pass. |
| 15 |
> > |
| 16 |
> > As an amd64 arch tester is ok for me to stabilize them. |
| 17 |
> > |
| 18 |
> > Any comments/problems? |
| 19 |
> I think it's OK to stabilize it on amd64. |
| 20 |
|
| 21 |
Done |
| 22 |
|
| 23 |
> |
| 24 |
> The bug #486552 is a major problem: nobody can compile any version of sbcl |
| 25 |
> on x86, starting from some moment between May and August 2013, due to some |
| 26 |
> change in something completely unrelated to sbcl. So, on x86 it definitely |
| 27 |
> should not be stabilized. |
| 28 |
> |
| 29 |
> By the way, the original reporter of this bug had this problem on an amd64 |
| 30 |
> system; only after he fully updated it to ~amd64, the problem had |
| 31 |
> disappeared. I suppose you have tested on a stable amd64, right? So, it |
| 32 |
> seems that the problem disappeared, and stabilizing on amd64 is OK. |
| 33 |
> |
| 34 |
|
| 35 |
I tested it on an stable amd64 system, no problems found apart from some |
| 36 |
'cosmetic' warnings found by repoman: |
| 37 |
|
| 38 |
ebuild.minorsyn 12 |
| 39 |
dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 50 |
| 40 |
dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 62 |
| 41 |
dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 51 |
| 42 |
dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 64 |
| 43 |
dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 57 |
| 44 |
dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 70 |
| 45 |
dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 57 |
| 46 |
dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 70 |
| 47 |
dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 57 |
| 48 |
dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 70 |
| 49 |
dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 56 |
| 50 |
dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 69 |
| 51 |
|
| 52 |
These are easy to fix though =) |
| 53 |
|
| 54 |
Will you take care of them? |
| 55 |
|
| 56 |
Thanks. |
| 57 |
|
| 58 |
Regards. |
| 59 |
|
| 60 |
> Andrey |
| 61 |
> |
| 62 |
|
| 63 |
-- |
Archives