| Summary: | shorewall6 service fails | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry ANIEL <thierry.aniel> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | thierry.aniel, vpisciot, wilcal.int |
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | shorewall-ipv6 | CVE: | |
| Status comment: | |||
|
Description
Thierry ANIEL
2013-05-19 15:56:00 CEST
Thierry ANIEL
2013-05-19 15:58:46 CEST
CC:
(none) =>
thierry.aniel duplicate *** This bug has been marked as a duplicate of bug 9723 *** Status:
NEW =>
RESOLVED
William Kenney
2013-05-23 23:05:35 CEST
CC:
(none) =>
wilcal.int I can confirm that the user must repeat the process of removing shorewall-ipv6 before every use of drakfirewall. I have found that a more permanent solution is to uninstall shorewall-ipv6 and then add it to the RPMDB rpm -ivh --justdb /media/mga3_64/x86_64/media/core/shorewall-ipv6-4.5.10.1-4.mga3.noarch.rpm drakfirewall, will still ask you to allow the install of "shorewall-ipv6" after the user confirms which ports they want to configure, but it seems that the install does not actually happen, as the entry is found in the RPMDB by the RPM installation routine. It's a bit messy, but at least you are able to use drakfirewall without any intermediate steps. CC:
(none) =>
vpisciot |