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 1763141 - can't install system-config-firewall: nothing provides python2-slip-dbus >= 0.2.7 needed by system-config-firewall-1.2.29-21.fc29.noarch
Summary: can't install system-config-firewall: nothing provides python2-slip-dbus >= 0...
Keywords:
Status: CLOSED DUPLICATE of bug 1701924
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-firewall
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Beveridge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-18 10:34 UTC by morgan read
Modified: 2019-10-20 22:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-20 22:31:29 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description morgan read 2019-10-18 10:34:13 UTC 
Description of problem:
$ sudo dnf install system-config-firewall
Last metadata expiration check: 0:03:16 ago on Fri 18 Oct 2019 11:24:24 BST.
Error: 
 Problem: conflicting requests
  - nothing provides python2-slip-dbus >= 0.2.7 needed by system-config-firewall-1.2.29-21.fc29.noarch
(try to add '--skip-broken' to skip uninstallable packages)

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

How reproducible:
always

Steps to Reproduce:
1. dnf install system-config-firewall
2.
3.

Actual results:
install fails

Expected results:
install succeeds

Additional info:
Comment 1 morgan read 2019-10-18 10:41:23 UTC 
firewall-config installs
is system-config-firewall depreciated?
Comment 2 morgan read 2019-10-18 11:02:55 UTC 
Sorry about all this noise - not running iptables anyway - I don't know if that means this ain't a bug?
Comment 3 David Beveridge 2019-10-20 22:31:29 UTC 
Yes, the package is End of Life

*** This bug has been marked as a duplicate of bug 1701924 ***
Note You need to log in before you can comment on or make changes to this bug.