Bug 1425050
| Summary: | System-config-firewall needs iptables-ipv6 package, which is not provided anymore | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zdenek Dohnal <zdohnal> |
| Component: | system-config-firewall | Assignee: | Thomas Woerner <twoerner> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | brian.murrell, djuran, laurent.rineau__fedora, rag, twoerner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:15:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Zdenek Dohnal
2017-02-20 12:50:03 UTC
+1 Bug #1327786 needs to be reverted or fixed in some way. Other packages besides system-config-firewall-base require iptables-ipv6, at least these other packages also have dependency on iptables-ipv6: shorewall-init-5.0.14.1-1.fc25.noarch shorewall-lite-5.0.14.1-1.fc25.noarch shorewall6-5.0.14.1-1.fc25.noarch shorewall6-lite-5.0.14.1-1.fc25.noarch There may be others. After dnf failed to upgrade iptables*, I downloaded the iptables*-1.6.0-3.fc25.x86_64 packages, and after comparing the file lists with the "old" iptables* packages, I decided to try to force an upgrade with "rpm -Uvh --nodeps iptables*.rpm". This seems to work, but, not surprisingly, after the upgrade, I get this: [nobody@nowhere ~]# dnf repoquery --unsatisfied Last metadata expiration check: 0:41:12 ago on Sun Mar 5 08:34:17 2017. nothing provides iptables-ipv6 needed by shorewall-init-5.0.14.1-1.fc25.noarch nothing provides iptables-ipv6 needed by shorewall-lite-5.0.14.1-1.fc25.noarch nothing provides iptables-ipv6 needed by shorewall6-5.0.14.1-1.fc25.noarch nothing provides iptables-ipv6 needed by shorewall6-lite-5.0.14.1-1.fc25.noarch -- 8< -- Minus spurious kernel and kmod* dependency errors¹ -- 8< -- -- 1. Since Fedora removes old packages from the updates repo, there are usually errors for installed, but not current kernel and kmod* packages (i.e. "none of the providers can be installed") that can be ignored. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's 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 Fedora 'version' of '25'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 Fedora 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. |