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

            Bug ID: 1775445
           Summary: Review Request: python-JuPyMake - Python wrapper for
                    the polymake shell
           Product: Fedora
           Version: rawhide
          Hardware: All
                OS: Linux
            Status: NEW
         Component: Package Review
          Severity: medium
          Priority: medium
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected]
  Target Milestone: ---
    Classification: Fedora



Spec URL: https://jjames.fedorapeople.org/python-JuPyMake/python-JuPyMake.spec
SRPM URL:
https://jjames.fedorapeople.org/python-JuPyMake/python-JuPyMake-0.9-1.20190509.031cc3a.fc32.src.rpm
RPMLINTRC URL:
https://jjames.fedorapeople.org/python-JuPyMake/python-JuPyMake.rpmlintrc
Fedora Account System Username: jjames
Description: This package provides a basic interface to call polymake from
python.  It is meant to be used in the Jupyter interface for polymake.

This package is currently built as part of the polymake SRPM.  I am extracting
it because it has a different version number and a different upstream from
polymake.

The cocoalib-devel and libnormaliz-devel BRs are only needed due to a bug in
the packaging of polymake, and will be removed soon when the polymake package
is fixed.  Similarly, the shared object winds up with an rpath (= %{_libdir}). 
That will also be fixed when polymake is updated.

-- 
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 -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to