Bug 216916 - Review Request: arpack - Fortran77 subroutines for solving large scale eigenvalue problems
Review Request: arpack - Fortran77 subroutines for solving large scale eigenv...
Status: CLOSED DUPLICATE of bug 214967
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jochen Schmitt
Fedora Package Reviews List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-22 12:37 EST by Dominik 'Rathann' Mierzejewski
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-22 17:27:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dominik 'Rathann' Mierzejewski 2006-11-22 12:37:58 EST
Spec URL: http://rpm.greysector.net/extras/arpack.spec
SRPM URL: http://rpm.greysector.net/extras/arpack-2.1-1.src.rpm
Description:
ARPACK is a collection of Fortran77 subroutines designed to solve large 
scale eigenvalue problems. 

The package is designed to compute a few eigenvalues and corresponding
eigenvectors of a general n by n matrix A. It is most appropriate for
large sparse or structured matrices A where structured means that a
matrix-vector product w <- Av requires order n rather than the usual
order n**2 floating point operations. This software is based upon an
algorithmic variant of the Arnoldi process called the Implicitly
Restarted Arnoldi Method (IRAM).
Comment 1 Jochen Schmitt 2006-11-22 13:50:20 EST
God:
+ Source package was not complainted by rpmlint.
* Local build works fine.
* Rpmlint is quited on binary packages.
* Local install/uninstall workds ok.
* Tarball matches with upstream.
* Mock build works fine.


Bad:
- Devel package should contains some documentation for developers.
I thins, that the stuff on /usr/doc/arpack-2.1/EXAMPLES shold be in
the developement package.
- Rpmlint complaints on installed package:
rpmlint arpack
W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 etime_
W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 slamch_
W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 cgemv_
W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 cscal_
--- A lot of simular lines ---
Comment 2 Dominik 'Rathann' Mierzejewski 2006-11-22 16:45:41 EST
(In reply to comment #1)
> Bad:
> - Devel package should contains some documentation for developers.
> I thins, that the stuff on /usr/doc/arpack-2.1/EXAMPLES shold be in
> the developement package.

Done, new specfile:
http://rpm.greysector.net/extras/arpack.spec
(SRPM unchanged)

> - Rpmlint complaints on installed package:

It doesn't here (FC6).

> rpmlint arpack
> W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 etime_
> W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 slamch_
> W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 cgemv_
> W: arpack undefined-non-weak-symbol /usr/lib/libarpack.so.2.1 cscal_
> --- A lot of simular lines ---

I have no idea what this is about.
Comment 3 Patrice Dumas 2006-11-22 16:57:46 EST
It seems to be a duplicate of #214967 so it should certainly be better
to add a comment on that report.

The symbols look like lapack symbols.
Comment 4 Dominik 'Rathann' Mierzejewski 2006-11-22 16:58:40 EST
Scratch that, I have an idea now. Stay tuned.
Comment 5 Dominik 'Rathann' Mierzejewski 2006-11-22 17:01:32 EST
Aw, crap. I forgot about #214967.
Comment 6 Dominik 'Rathann' Mierzejewski 2006-11-22 17:19:24 EST
OK, non-weak symbol issue fixed.

http://rpm.greysector.net/extras/arpack.spec
http://rpm.greysector.net/extras/arpack-2.1-2.src.rpm

I will ask Axel if he would consider letting me (co-)maintain this.
Comment 7 Dominik 'Rathann' Mierzejewski 2006-11-22 17:27:52 EST

*** This bug has been marked as a duplicate of 214967 ***

Note You need to log in before you can comment on or make changes to this bug.