Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1431571 - python-lib389: python3-lib389 requires both Python 2 and Python 3
Summary: python-lib389: python3-lib389 requires both Python 2 and Python 3
Alias: None
Product: Fedora
Classification: Fedora
Component: python-lib389
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: mreynolds
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: PYTHON3
TreeView+ depends on / blocked
Reported: 2017-03-13 10:10 UTC by Iryna Shcherbina
Modified: 2017-03-22 22:02 UTC (History)
1 user (show)

Fixed In Version: python-lib389-1.0.3-2.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-03-22 22:02:59 UTC
Type: Bug

Attachments (Terms of Use)

Description Iryna Shcherbina 2017-03-13 10:10:45 UTC
The python3-lib389 RPM requires both Python 2 and Python 3.

Except in very special circumstances, there is no need for one package
to drag in both Python stacks. Usually, this is a packaging error: for
example, a stray "/usr/bin/python" shebang in a Python 3 package can
introduce a Python 2 dependency.

Please split your package, or remove the stray dependencies.
There is a section on shebangs in the Python RPM Porting Guide [0]
which covers this issue.

Besides this, the package is building two identical Python 2 subpackages, python-lib389 and python2-lib389. Only python2-lib389 should be built, which should provide both names.

It's ok to do this in Rawhide only, however, it would be greatly
appreciated if you could push it to Fedora 25 as well.

If anything is unclear, or if you need any kind of assistance, you can
ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy
to help investigating or fixing this issue!


Comment 1 mreynolds 2017-03-13 13:48:46 UTC
I'll investigate this.  I was trying to port someone else's changes to this spec file.  I might need help, but let me see what I can do first.  Thanks!

Comment 2 mreynolds 2017-03-17 18:48:43 UTC

I was able to remove the duplicate package.  New builds are listed above.

Comment 3 Iryna Shcherbina 2017-03-22 22:02:59 UTC
Thank you for the change. Closing the issue.

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