Summary: | sci-libs/suitesparse-5.4.0 stabilisation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Sturmlechner <asturm> |
Component: | Stabilization | Assignee: | Michael Orlitzky <mjo> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | frp.bissey, sci, sparc, waebbl-gentoo |
Priority: | Normal | Keywords: | PullRequest, STABLEREQ |
Version: | unspecified | Flags: | nattka:
sanity-check+
|
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=716982 https://github.com/gentoo/gentoo/pull/15920 |
||
Whiteboard: | |||
Package list: |
sci-libs/suitesparse-5.4.0
sci-libs/suitesparseconfig-5.4.0
sci-libs/amd-2.4.6
sci-libs/btf-1.2.6
sci-libs/camd-2.4.6
sci-libs/ccolamd-2.9.6
sci-libs/cholmod-3.0.13
sci-libs/colamd-2.9.6
sci-libs/cxsparse-3.2.0
sci-libs/klu-1.3.9
sci-libs/ldl-2.2.6
sci-libs/spqr-2.0.9
sci-libs/umfpack-5.7.9
sci-libs/metis-5.1.0-r4
dev-cpp/tbb-2019.8 sparc
|
Runtime testing required: | --- |
Bug Depends on: | 729634, 729636, 713582 | ||
Bug Blocks: | 698100 |
Description
Andreas Sturmlechner
2020-04-10 16:52:27 UTC
We should stabilize all of suitesparse at once, most likely, but first I want the fix from his PR =) That already happened, picked in commit 0b6f695a. I'm happy with this, but we have to remove the old 5.6.2 then ASAP after stablizing this one, to get rid of the CI issue. Targets: amd64, arm64, ppc, ppc64, x86, and sparc (who all have sci-libs/suitesparseconfig-4.2.1-r1 stable). Before we can do that, we need a few things keyworded: sci-libs/suitesparse: arm64, ppc, ppc64, sparc sci-libs/btf: arm64 sci-libs/cxsparse: arm64 sci-libs/klu: arm64, ppc, ppc64, sparc sci-libs/ldl: arm64 sci-libs/spqr: arm64, sparc I'll open a blocker for those. Is there any good reason to wait any longer here? (In reply to Andreas Sturmlechner from comment #5) > Is there any good reason to wait any longer here? Many of these packages don't even have keywords on the arches that need to be stabilized, so we're waiting on bug 716982... (In reply to Michael Orlitzky from comment #6) > (In reply to Andreas Sturmlechner from comment #5) > > Is there any good reason to wait any longer here? > > Many of these packages don't even have keywords on the arches that need to > be stabilized, so we're waiting on bug 716982... You don't have to wait for the very last (~hppa) arch to finish keywording for starting stabilisation here. You may even go as far as drop sci-libs/umfpack to ~hppa later, seeing how there is no stable revdep. (In reply to Andreas Sturmlechner from comment #8) > You may even go as far as drop sci-libs/umfpack to ~hppa later, seeing how > there is no stable revdep. That sounds OK. I'm on a tiny laptop at the moment about to "walk into" a seminar, so if you want to kick this off, feel free. Okay then, arches please stabilise. Sanity check failed:
> sci-libs/cholmod-3.0.13
> depend ppc stable profile default/linux/powerpc/ppc32/17.0 (27 total)
> >=sci-libs/metis-5.1.0
> sci-libs/parmetis
> rdepend ppc stable profile default/linux/powerpc/ppc32/17.0 (27 total)
> >=sci-libs/metis-5.1.0
> sci-libs/parmetis
> depend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total)
> >=sci-libs/metis-5.1.0
> sci-libs/parmetis
> rdepend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total)
> >=sci-libs/metis-5.1.0
> sci-libs/parmetis
> sci-libs/spqr-2.0.9
> depend amd64 stable profile default/linux/amd64/17.0 (67 total)
> >=sci-libs/metis-5.1.0
> depend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total)
> >=sci-libs/metis-5.1.0
> rdepend amd64 stable profile default/linux/amd64/17.0 (67 total)
> >=sci-libs/metis-5.1.0
> rdepend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (4 total)
> >=sci-libs/metis-5.1.0
> depend sparc stable profile default/linux/sparc/17.0 (8 total)
> >=sci-libs/metis-5.1.0
> dev-cpp/tbb
> rdepend sparc stable profile default/linux/sparc/17.0 (8 total)
> >=sci-libs/metis-5.1.0
> dev-cpp/tbb
Unable to check for sanity:
> no match for package: sci-libs/metis-5.1.0
ppc stable ppc64 stable amd64 stable arm64 stable Half of the packages fail build with USE=doc because of sandbox violations of TeX things. I was told it's basically the VARTEXFONTS workaround in the ebuilds. x86 stable Pending Cleanup-CI-Run. |