[Bug 233975] Review Request: freefem++ - PDE solving tool

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: freefem++ - PDE solving tool


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233975





------- Additional Comments From rpm at greysector.net  2007-04-28 15:53 EST -------
(In reply to comment #2)
> REVIEW:
> 
>  * %{?dist} tag's present
>  * package's licensed under LGPL and license's included in package
> !* rpmlint output:
> 
> W: freefem++-glx non-standard-group Applications/Scientific
> 
> Why don't use Applications/Engineering as in the main package?

Copy & paste error from an old version.

> W: freefem++-glx no-documentation
> E: freefem++ binary-or-shlib-defines-rpath /usr/bin/FreeFem++-client ['/usr/
> lib64']
> E: freefem++ binary-or-shlib-defines-rpath /usr/bin/FreeFem++-cs ['/usr/lib64']
> E: freefem++ binary-or-shlib-defines-rpath /usr/bin/FreeFem++-ide ['/usr/lib64']
> 
> Has to be fixed. Unfortunately, I'm currently unable to check if the way to fix 
> the rpath from PackagingGuidelines works for this package, but it should be 
> checked.

Can't fix. The bug is in fltk package. See bug 214967.

> W: freefem++ spurious-executable-perm /usr/share/man/man1/FreeFem++.1.gz
> 
> Change wrong permissions

Will fix.

> E: freefem++-debuginfo script-without-shebang /usr/src/debug/freefem++-2.14-1/
> src/fflib/mt19937ar.cpp
> E: freefem++-debuginfo script-without-shebang /usr/src/debug/freefem++-2.14-1/
> src/lglib/mymain.cpp

Will fix.

> W: freefem++-mpi non-standard-group Applications/Scientific
> W: freefem++-mpi no-documentation
> 
>  * md5sums match each other. However, 2.14 is not the newest freefem++'s 
> release so you have to package the newer version

OK.

>  * BRs seem to be proper, mock fc6/x86_64 builds fine

But devel doesn't. I'm working on this right now.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.