[Bug 1519834] Review Request: BOUT++ - Computational fluid simulation library for curvi-linear geometries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



--- Comment #3 from david08741@xxxxxxxxx ---
I fixed the setup-not-quite warning.

By now BOUT++ has also a python interface, which is packaged for python3.

A debug package is built, as support for shared objects was added.

The new rpmlint warnings are:
$ rpmlint bout++.spec noarch/* x86_64/*
bout++.spec:88: W: unversioned-explicit-provides bundled(libpvode)
bout++.spec:139: W: unversioned-explicit-provides bundled(libpvode)
bout++-common.noarch: W: spelling-error %description -l en_US curvilinear ->
rectilinear
bout++-doc.noarch: W: spelling-error %description -l en_US curvilinear ->
rectilinear
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz 5043:
normal or special character expected (got a space)
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz 5097:
warning: numeric expression expected (got `o')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz 5194:
warning: numeric expression expected (got `r')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz 5200:
warning: numeric expression expected (got `r')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz 5261:
warning: numeric expression expected (got `r')
[...]
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
35289: warning: numeric expression expected (got `\e')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
46583: `m' is an invalid argument to \O
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
59851: warning: numeric expression expected (got `g')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
59852: warning: numeric expression expected (got `g')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
59857: warning: numeric expression expected (got `g')
bout++-doc.noarch: W: manual-page-warning /usr/share/man/man1/bout++.1.gz
59857: warning: numeric expression expected (got `g')
python3-bout++.noarch: W: spelling-error %description -l en_US pre -> per, ore,
pee
python3-bout++.noarch: W: no-documentation
bout++-mpich.x86_64: W: spelling-error %description -l en_US curvilinear ->
rectilinear
bout++-mpich.x86_64: W: no-documentation
bout++-mpich-devel.x86_64: W: spelling-error %description -l en_US curvilinear
-> rectilinear
bout++-mpich-devel.x86_64: W: only-non-binary-in-usr-lib
bout++-mpich-devel.x86_64: W: no-documentation
bout++-openmpi.x86_64: W: spelling-error %description -l en_US curvilinear ->
rectilinear
bout++-openmpi.x86_64: W: no-documentation
bout++-openmpi-devel.x86_64: W: spelling-error %description -l en_US
curvilinear -> rectilinear
bout++-openmpi-devel.x86_64: W: only-non-binary-in-usr-lib
bout++-openmpi-devel.x86_64: W: no-documentation
python3-bout++-mpich.x86_64: W: no-documentation
python3-bout++-openmpi.x86_64: W: spelling-error Summary(en_US) mpich -> chimp
python3-bout++-openmpi.x86_64: W: no-documentation
15 packages and 1 specfiles checked; 0 errors, 186 warnings.

I am uncertain about the man page warnings - I don't think it is worth fixing
them, as the man page is generated by sphinx. Is it better to not shop the man
page, or ship a potentially broken one?
More troublesome to me seems the fact that I cannot find and open the man page
after installing the rpm with dnf. If I download with dnf, and install with
rpm, the man page is available. Any ideas why that might be happening?

BOUT++ comes with libpvode - I would like to ship the bundled upstream version
to give the same results as the upstream code. From [1] it seems ok to bundle.
BOUT++ can be build with more recent versions, but they are not packaged.

The only-non-binary-in-usr-lib is due to mpi - the specific header files are
located in the mpi folders.

The rawhide build fails on copr, but is fine with koji scratch builds. I was
also unable to reproduce this issue locally with mock or a container. Not sure
why there are illegal instructions.

Updated Spec:
https://github.com/dschwoerer/bout-spec/raw/master/bout%2B%2B.spec
New Builds: https://copr.fedorainfracloud.org/coprs/davidsch/bout/build/833821/

[1] https://fedoraproject.org/wiki/Bundled_Libraries

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux