Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43017 - [firewalld] move networkmanager to optional dependencies
Attached to Project:
Community Packages
Opened by David Runge (dvzrv) - Friday, 05 December 2014, 14:43 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 08 December 2014, 09:19 GMT
Opened by David Runge (dvzrv) - Friday, 05 December 2014, 14:43 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 08 December 2014, 09:19 GMT
|
DetailsDescription: networkmanager is not a dependency of firewalld, as such it should not be treated as one, but instead be moved to "Optional Deps".
Additional info: https://fedorahosted.org/released/firewalld/firewalld-0.3.13.tar.bz2 (README inside doesn't mention networkmanager as a direct dependency) https://fedoraproject.org/wiki/FirewallD#Network_connections_handled_by_network_scripts (wiki doesn't mention networkmanager as a direct dependency) |
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Monday, 08 December 2014, 09:19 GMT
Reason for closing: Fixed
Additional comments about closing: 0.3.13-1
Monday, 08 December 2014, 09:19 GMT
Reason for closing: Fixed
Additional comments about closing: 0.3.13-1
Did you try using it without networkmanager? You'd need to use firewall-cmd to configure then. firewall-config makes it so much easier to configure and wasn't an optional feature imho, thus adding NM to the depends seemed like the right choice. But if there are some people going cmd only, I guess it makes sense to demote it.
What about headless systems though? Isn't that what firewall-cmd is for eventually?
I'm using firewalld on at least one headless machine, and although firewall-cmd could use improvement in usability, it's still quite handy in managing firewalls.