Impossible to add a remote printer

Sat Feb 7 12:02:43 UTC 2015

On 02/06/2015 11:47 PM, poma wrote:
> On 06.02.2015 14:05, Thomas Woerner wrote:
>> On 02/05/2015 06:57 PM, poma wrote:
>>> On 04.02.2015 20:08, poma wrote:
>>>> On 03.02.2015 18:15, poma wrote:
>>>>> On 03.02.2015 11:07, Thomas Woerner wrote:
>>>>>> On 02/02/2015 05:55 PM, poma wrote:
>>>>>>> On 02.02.2015 17:49, poma wrote:
>>>>>>>> On 02.02.2015 17:36, Tim Waugh wrote:
>>>>>>>>> On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
>>>>>>>>>> can this mechanism be improved in the way when you chose not to want
>>>>>>>>>> to share the printer that the relevant port is closed?
>>>>>>>>>
>>>>>>>>> Is there a sane way of doing that though? I think applications wanting
>>>>>>>>> to 'reset' ports for a zone would need to know what the default was to
>>>>>>>>> start with.
>>>>>>>>>
>>>>>>>>> Tim.
>>>>>>>>> */
>>>>>>>>>
>>>>>>>>
>>>>>>>> I really do not understand what should be an obstacle. :)
>>>>>>>> Just to close the port that is no longer used, the same way that we opened.
>>>>>>>>
>>>>>>>
>>>>>>> Mister Woerner, Popelka care to comment?
>>>>>>> Perhaps I missed some technicalities related.
>>>>>>>
>>>>>>>
>>>>>> I think it would make sense to be able to see if ipp* was enabled in the
>>>>>> initial configuration of a zone. Right now this is not possible.
>>>>>>
>>>>>> We might be able to add interfaces to get initial zone, service etc.
>>>>>> configuration settings.
>>>>>>
>>>>>> Regards,
>>>>>> Thomas
>>>>>>
>>>>>
>>>>> I think I understand, but I also think that I did not understand.
>>>>> Cogito ergo sum.
>>>>>
>>>>>
>>>>
>>>> https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24
>>>> Future Features:
>>>>
>>>> - reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
>>>>
>>>> If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
>>>>
>>>>
>>>>
>>>
>>> Mister Woerner, Popelka please consider, so users don't get confused further.
>>> There is no real reason to wait for Fedora 22.
>>>
>>
>> I think there is, because switching to Python3 also in Fedora 21 will
>> change requirements for already installed systems and also for fresh
>> installations. This will result in having both Python versions in the
>> default installation.
>>
>> With Python3 as the default python interpreter in Fedora 22 this is
>> expected there, but not in Fedora 21.
>>
>
>
> If possible I would appreciate clearer explanation.
>
> To gain "publish shared printers" functionality in 'system-config-printer', required is to install 'python3-firewall'.
> Will it be done manually
> # yum install python3-firewall
> or the 'python3-firewall' will be automatically pulled by the main package
> # yum update firewalld
> it still has to be done.
> The only difference is that in the second case it works on more friendly way.
>
With a requirement of python2-firewall and python3-firewall we end up 
with the same situation: Both Python versions are installed - even if 
they are not used.

For now I do not have a solution besides adding a requirement for 
python3-firewall to system-config-printer. The impact might be small 
enough with these requirements of python3-firewall:

python(abi) = 3.4
python3-dbus
python3-decorator
python3-gobject
python3-slip-dbus
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1

Tim, what do you think?

Regards,
Thomas

>
>>> ---
>>>    firewalld.spec | 8 ++++++--
>>>    1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/firewalld.spec b/firewalld.spec
>>> index 06b5b05..7727644 100644
>>> --- a/firewalld.spec
>>> +++ b/firewalld.spec
>>> @@ -1,6 +1,6 @@
>>>    %if (0%{?fedora} >= 13 || 0%{?rhel} >= 7)
>>>    %define with_python3 1
>>> -%if (0%{?fedora} >= 22 || 0%{?rhel} >= 8)
>>> +%if (0%{?fedora} >= 21 || 0%{?rhel} >= 8)
>>>    %define use_python3 1
>>>    %endif
>>>    %endif
>>> @@ -8,7 +8,7 @@
>>>    Summary: A firewall daemon with D-Bus interface providing a dynamic firewall
>>>    Name: firewalld
>>>    Version: 0.3.13
>>> -Release: 2%{?dist}
>>> +Release: 3%{?dist}
>>>    URL:     http://www.firewalld.org
>>>    License: GPLv2+
>>>    Source0: https://fedorahosted.org/released/firewalld/%{name}-%{version}.tar.bz2
>>> @@ -413,6 +413,10 @@ fi
>>>    %endif
>>>
>>>    %changelog
>>> +* Thu Feb 05 2015 poma <poma at gmail.com> - 0.3.13-3
>>> +- use python3 bindings also on Fedora 21 for "publish shared printers"
>>> +  functionality in system-config-printer
>>> +
>>>    *  Wed Jan 28 2015 Thomas Woerner <twoerner at redhat.com> - 0.3.13-2
>>>    - enable python2 and python3 bindings for fedora >= 20 and rhel >= 7
>>>    - use python3 bindings on fedora >= 22 and rhel >= 8 for firewalld,
>>>
>>
>> Regards,
>> Thomas
>>
>

-- 
Thomas Woerner
Senior Software Engineer     Phone: +49-711-96437-310
Red Hat GmbH                 Fax  : +49-711-96437-111
Wankelstrasse 5              Email: Thomas Woerner <twoerner at redhat.com>
70563 Stuttgart              Web  : http://www.redhat.de/