FS#50893 - [suitesparse] now provides metis

Attached to Project: Arch Linux
Opened by viperpaulo (viperpaulo) - Monday, 26 September 2016, 09:02 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 12 October 2016, 09:27 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
According to SuiteSparse changelog, SuiteSparse is now providing metis:
Jan 30, 2016: SuiteSparse 4.5.0
* CHOLMOD now uses METIS 5.1.0, which is distributed with SuiteSparse

It is thus conflicting with AUR/metis (5.1.0.p1-2) needed for example by mumps or parmetis:
suitesparse: /usr/include/metis.h exists in filesystem
suitesparse: /usr/lib/libmetis.so exists in filesystem


Additional info:
* package version(s) 4.5 or higher (actually 4.5.3)
* config and/or log files etc.


Steps to reproduce:
* install AUR/metis
* install extra/suitesparse
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 12 October 2016, 09:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  suitesparse 4.5.3-2
Comment by viperpaulo (viperpaulo) - Monday, 26 September 2016, 11:33 GMT
I think those files will be needed too:
/usr/include/gklib_defs.h
/usr/include/gklib_rename.h
/usr/include/gklib_tls.h
Comment by Antonio Rojas (arojas) - Monday, 26 September 2016, 12:19 GMT
Do you know if Tim Davis plans to maintain metis himself from now on, or did he just include the latest metis release? I couldn't find any info on his website. In the latter case I guess it would be better to package metis separately.
Comment by viperpaulo (viperpaulo) - Tuesday, 27 September 2016, 08:58 GMT
You right, I asked myself the same question! Though maybe the best is to remove those conflicting files from this package and let a separate package for metis.
Comment by Ronald van Haren (pressh) - Tuesday, 27 September 2016, 14:19 GMT
Yes, just building against an existing metis install should fix it. I'll see if I can do it one of these days.
Comment by Jed Brown (jedbrown) - Wednesday, 12 October 2016, 04:09 GMT
METIS is basically unmaintained upstream and patches are carried by many downstream packages. AUR metis currently uses the patches carried by the PETSc project because they are responsive. As the current maintainer of AUR metis, I would not have a problem with letting suitesparse "provide" metis, but it would need to include the gklib*.h files mentioned above. I think the alternative is to promote metis to extra, which is also okay with me.

Loading...