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 bugzilla.redhat.com.
Bug 1566618 - policycoreutils: policycoreutils-gui requires both Python 2 and Python 3
Summary: policycoreutils: policycoreutils-gui requires both Python 2 and Python 3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3 1567354
TreeView+ depends on / blocked
 
Reported: 2018-04-12 15:51 UTC by Petr Viktorin (pviktori)
Modified: 2018-04-19 07:15 UTC (History)
5 users (show)

Fixed In Version: policycoreutils-2.7-20.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-19 07:15:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Remove python2 sepolicy gui leftovers (deleted)
2018-04-12 19:23 UTC, Petr Lautrbach
no flags Details | Diff

Description Petr Viktorin (pviktori) 2018-04-12 15:51:08 UTC
The policycoreutils-gui 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.

Please split your package, or remove one of the versions of sepolicy.gui.

It's OK to do this in Rawhide only, however, it would be greatly
appreciated if you could push it to Fedora 28 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 Petr Lautrbach 2018-04-12 19:23:32 UTC
Created attachment 1421029 [details]
Remove python2 sepolicy gui leftovers


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