Bug 744193 - The package does not add the extra command 'build_sphinx'
Summary: The package does not add the extra command 'build_sphinx'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-sphinx10
Version: el6
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Michel Alexandre Salim
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-07 12:13 UTC by Paolo Smiraglia
Modified: 2020-11-30 15:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:55:49 UTC
Type: ---


Attachments (Terms of Use)

Description Paolo Smiraglia 2011-10-07 12:13:58 UTC
Description of problem:

After installing the package python-sphinx10, the extra command 'build_sphinx' is not shown in the list of extra commands that appears as the output for the command

   python setup.py --help-commands

launched within the source directory of OpenStack Swift.


Version-Release number of selected component (if applicable):

   1.0.4-4.el6


How reproducible:

Install the package python-sphinx10 using yum.


Steps to Reproduce:

1. yum install python-sphinx10
  
Actual results:

'build_sphinx' option does not appear in the extra commands list generated by python-setuptools.


Expected results:

We aspect an option like 'build_sphinx10' in order to not interfere with the package python-sphinx.


Additional info:

Comment 1 John Morris 2012-09-04 16:15:13 UTC
Hi Paolo, not sure why nobody's addressed this until now.  I had this same problem.

Look at /usr/share/doc/python-sphinx10-1.0.8/README.Fedora, which explains how to set your PYTHONPATH.

I used this, and it worked perfectly:

PYTHONPATH=/usr/lib/python2.6/site-packages/Sphinx-1.*.egg ./setup.py build_sphinx

    John

Comment 2 Ben Cotton 2020-11-05 16:51:47 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-05 16:54:28 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-30 15:55:49 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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