Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 645954

Summary: dev-lisp/sbcl-1.3.21 stabilization request
Product: Gentoo Linux Reporter: Dawid E. <eckertdawid>
Component: StabilizationAssignee: Stelian Ionescu <bugs>
Status: RESOLVED OBSOLETE    
Severity: normal CC: bugs, common-lisp, proxy-maint, t-mo
Priority: Normal Keywords: STABLEREQ
Version: unspecifiedFlags: stable-bot: sanity-check+
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
=dev-lisp/sbcl-1.3.21
Runtime testing required: Yes
Bug Depends on: 646812    
Bug Blocks: 639898, 652808    

Description Dawid E. 2018-01-28 13:07:33 UTC
The current version marked as stable fails to build on the newer 17.0 profiles.
Comment 1 Chema Alonso Josa (RETIRED) gentoo-dev 2018-01-29 21:51:44 UTC
Please stabilize.

Thanks in advance
Comment 2 Thomas Deutschmann (RETIRED) gentoo-dev 2018-02-06 18:09:59 UTC
x86 stopped stabilization due to bug 646812.
Comment 3 Aaron Bauman (RETIRED) gentoo-dev 2018-03-30 16:10:42 UTC
Please CC arches when fixed.
Comment 4 Sergei Trofimovich (RETIRED) gentoo-dev 2018-04-01 14:18:30 UTC
ppc stable
Comment 5 Larry the Git Cow gentoo-dev 2018-04-08 19:05:37 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf334f13c58b0f8771548e7e597198cefbc4dc75

commit bf334f13c58b0f8771548e7e597198cefbc4dc75
Author:     Aaron Bauman <bman@gentoo.org>
AuthorDate: 2018-04-08 19:04:31 +0000
Commit:     Aaron Bauman <bman@gentoo.org>
CommitDate: 2018-04-08 19:04:31 +0000

    dev-lisp/sbcl: amd64 stable
    
    Bug: https://bugs.gentoo.org/645954
    Package-Manager: Portage-2.3.28, Repoman-2.3.9

 dev-lisp/sbcl/sbcl-1.3.21.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)}
Comment 6 Stabilization helper bot gentoo-dev 2019-03-16 11:00:25 UTC
An automated check of this bug failed - the following atom is unknown:

dev-lisp/sbcl-1.3.21

Please verify the atom list.
Comment 7 Stabilization helper bot gentoo-dev 2019-03-16 13:00:35 UTC
An automated check of this bug succeeded - the previous repoman errors are now resolved.
Comment 8 Rolf Eike Beer archtester 2019-03-16 19:39:31 UTC
Replaced by bug 662244