Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority
On Thursday, May 07 2015, Frederic Peters wrote:
>> What's the real point of this package? One actually needs to install
>> the tax-report-building program from RFB (IRPF20xx) to have anything for
>> rnetclient to transmit, at which point you might as well install
>> ReceitaNet since you're already running RFB-provided java code anyway.
>
> It looks like the initial part wouldn't require network access; this
> would be quite an important difference.
I'm not sure I understood the sentence, but yeah, the program used to
prepare the tax report indeed does not need network access.
>> Regardless of whether the process of reverse engineering the ReceitaNet
>> protocol is legal or not (I don't know, so I am not assuming anything),
>> actually connecting to RFB servers using this program might well not be
>> legal.
>
> I don't know anything about Brazilian reverse engineering, or others,
> laws, and what would apply here. But I wouldn't stop at "regardless
> it is legal or not" and "might not well be legal" without any details.
Thanks, that's my feeling as well. And that's why those programs were
developed. But as I said in my reply to Henrique, reverse engineering
is not against the Brazilian copyright law.
>> Also, ReceitaNet is often updated, it went from version 4 (tax report of
>> 2014) to version 7 (tax report of 2015), rnetclient would have to be
>> kept up-to-date if such changes in ReceitaNet are in any way related to
>> the protocol or servers it should connect to submit the tax report.
>> This can cause operational issues if rnetclient makes it to Debian
>> stable, since the program must be working perfectly during the tax
>> submission window.
>>
>> In fact, the upstream homepage has this notice (loosely translated from
>> pt_BR):
>> "Version 2015.0 did not support fully the tax report format for 2015.
>> This problem has been fixed in version 2015.1. We wait reports of both
>> sucessful and non-sucessful use of rnetclient 2015.1 in our mailing
>> list".
>
> This makes it an appropriate candidate for jessie-updates.
That is actually a pretty good solution! I am still learning the terms
and the whole process here, but jessie-updates, according to:
<https://www.debian.org/News/2011/20110215>
(thanks to Cascardo for providing the link)
would indeed be the ideal place for rnetclient, according to this
criterion:
- Packages that need to be current to be useful (e.g. clamav).
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
Reply to: