Re: removal of python2-firewall
On Wed, May 23, 2018 at 10:06:08PM -0500, Adam Miller wrote:
> Do we need to reintroduce it?
I think from a Fedora user perspective, it would be nice to reintroduce it
for Fedora 28 just because Ansible is still shipping python2 by default.
Retiring python2-firewall in Fedora 29 makes sense given the impending
change to Ansible being python3 only.
However from an upstream Ansible
perspective, if there is a strong case not to re-introduce it in Fedora
then I don't have a hard preference because it's relatively easy to direct
users to the module documentation informing them of the change and the need
to use python3 mode (which is now even more clear on the specific issue
thanks to the results of the bugzilla referenced previously in this thread).
I agree that the proposed workaround is actually nicer. Instead of
installing python2-firewall package on managed fedora machines, one
would just tweak ansible_python_interpreter variable without installing
anything on managed machines (firewalld requires python3-firewall, so it
will be already there). Moreover ansible already supports python3
upstream and Fedora seems to plan to do the switch in next release,
which is quite coold and I was not fully aware about it.
From this point of view, reintroduction is not necessary.
Another good thing about upcoming python3 switch is that we don't have
to worry about dropping python2 subpackages required by ansible, but not
tracked in requirements, by mistake.
That said, the main (and now the only) reason for reintroduction of
python2-firewall subpackage is to prevent distrupting people who solved
the issue with firewalld ansible module in the past[1] and now it stops
working wihtout any announcement. And obviously the reintroduction would
help only people who haven't upgraded (or reconfiugred firewalld) yet.
[1] eg. my role
https://github.com/marbu/fedora-post-install/blob/cef286937a4e577e092750f...
--
Martin Bukatovic