Summary: | sci-libs/spqr-1.2.3-r1 : * Failed Running automake ! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | frp.bissey, gentoo_bugs.nu_q5v, kingjon3377, luisav.ferreira, molari.alessandro, O01eg, treecleaner, xianwen.chen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 627094 | ||
Bug Blocks: | 613576 | ||
Attachments: |
automake.out
emerge-history.txt environment sci-libs:spqr-1.2.3-r1:20160620-215840.log |
Description
Toralf Förster
2016-06-21 16:17:04 UTC
Created attachment 438268 [details]
automake.out
Created attachment 438270 [details]
emerge-history.txt
Created attachment 438272 [details]
environment
Created attachment 438274 [details]
sci-libs:spqr-1.2.3-r1:20160620-215840.log
Are there any news? I'm still getting the same error. The stable version sci-libs/1.2.3-r1 is affected by the automake bug, but the version 1.3.1 (~amd64, in portage tree) builds. This problem still exists I have a more recent version of spqr in the sage-on-gentoo overlay which should have any issues. I offered to proxy-maintain on another suitesparse related bug. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1703eb051609561a08bf1f267a30e9e68f9ef60a commit 1703eb051609561a08bf1f267a30e9e68f9ef60a Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2020-03-02 00:44:48 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2020-03-02 17:20:46 +0000 sci-libs/spqr: new version 2.0.9. Update to EAPI=7 and fix the HOMEPAGE, SRC_URI, and LICENSE. This is part of a larger SuiteSparse v5.4.0 upgrade thanks to François Bissey whose sage-on-gentoo ebuilds I'm using. There's a newer release (v5.7.1) of SuiteSparse, but v5.4.0 has seen more testing. This version uses a "partition" USE flag instead of "metis", to more closely match the terminology used upstream and by sci-libs/cholmod. Bug: https://bugs.gentoo.org/492484 Bug: https://bugs.gentoo.org/586582 Bug: https://bugs.gentoo.org/654548 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> sci-libs/spqr/Manifest | 1 + sci-libs/spqr/metadata.xml | 4 ++++ sci-libs/spqr/spqr-2.0.9.ebuild | 33 +++++++++++++++++++++++++++++++++ 3 files changed, 38 insertions(+) (In reply to Larry the Git Cow from comment #9) > The bug has been referenced in the following commit(s): > > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=1703eb051609561a08bf1f267a30e9e68f9ef60a > > commit 1703eb051609561a08bf1f267a30e9e68f9ef60a > Author: Michael Orlitzky <mjo@gentoo.org> > AuthorDate: 2020-03-02 00:44:48 +0000 > Commit: Michael Orlitzky <mjo@gentoo.org> > CommitDate: 2020-03-02 17:20:46 +0000 > > sci-libs/spqr: new version 2.0.9. > > Update to EAPI=7 and fix the HOMEPAGE, SRC_URI, and LICENSE. This is > part of a larger SuiteSparse v5.4.0 upgrade thanks to François Bissey > whose sage-on-gentoo ebuilds I'm using. There's a newer release > (v5.7.1) of SuiteSparse, but v5.4.0 has seen more testing. > > This version uses a "partition" USE flag instead of "metis", to more > closely match the terminology used upstream and by sci-libs/cholmod. > > Bug: https://bugs.gentoo.org/492484 > Bug: https://bugs.gentoo.org/586582 > Bug: https://bugs.gentoo.org/654548 > Package-Manager: Portage-2.3.84, Repoman-2.3.20 > Signed-off-by: Michael Orlitzky <mjo@gentoo.org> > > sci-libs/spqr/Manifest | 1 + > sci-libs/spqr/metadata.xml | 4 ++++ > sci-libs/spqr/spqr-2.0.9.ebuild | 33 +++++++++++++++++++++++++++++++++ > 3 files changed, 38 insertions(+) |