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

            Bug ID: 1400271
           Summary: Review Request: python-sphinxcontrib-pecanwsme -
                    Extension to Sphinx for documenting APIs built with
                    Pecan and WSME
           Product: Red Hat OpenStack
           Version: 11.0 (Ocata)
         Component: distribution
          Severity: medium
          Priority: medium
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected],
                    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected],
                    [email protected],
                    [email protected], [email protected],
                    [email protected]
        Depends On: 1283327
             Group: private



BuildRequires *only* for openstack-mistral in ocata (do not ship)

+++ This bug was initially created as a clone of Bug #1283327 +++

Spec URL:
https://jpena.fedorapeople.org/python-sphinxcontrib-pecanwsme/python-sphinxcontrib-pecanwsme.spec
SRPM URL:
https://jpena.fedorapeople.org/python-sphinxcontrib-pecanwsme/python-sphinxcontrib-pecanwsme-0.8.0-1.fc24.src.rpm
Description: Extension to Sphinx for documenting APIs built with Pecan and WSME
Fedora Account System Username: jpena

Koji scratch build available at
http://koji.fedoraproject.org/koji/taskinfo?taskID=11893963

Please note the Python 3 subpackage is currently disabled, due to lack of
upstream support (see
https://github.com/dreamhost/sphinxcontrib-pecanwsme/pull/14).


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1283327
[Bug 1283327] Review Request: python-sphinxcontrib-pecanwsme - Extension to
Sphinx for documenting APIs built with Pecan and WSME
-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to