From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 136: Calamaris proxy reports stay empty
Date: Wed, 13 Nov 2019 16:58:20 +0000 [thread overview]
Message-ID: <AACA7F30-0889-4601-A799-9B59779604CF@ipfire.org> (raw)
In-Reply-To: <18eb03fa-0045-4565-d889-e910c1ff4670@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Matthias, you are not copying the list any more in most of your emails...
> On 12 Nov 2019, at 19:05, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 12.11.2019 13:53, Michael Tremer wrote:
>> Hi,
>>
>>> On 11 Nov 2019, at 17:17, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> On 11.11.2019 14:14, Michael Tremer wrote:
>>>> ...
>>>> Did you try changing this line as suggested?
>>>
>>> No, because I'm not that familiar with Perl. How would I do this?
>>>
>>> Line 2609ff reads:
>>>
>>> ...
>>> if ( defined(%tcp_content) ) {
>>
>> I think this line should just be:
>>
>> if (%tcp_content) {
>
> Done.
>
> Tested.
>
> Worked on both machines.
>
> Thanks. ;-)
Cool. Please submit a patch which we can release as a quick bug fix.
>> You might have more of those in the file, but I am sure the interpreter will tell you when you try to run it.
>>
>> As far as I know this whole calamaris thing is not maintained upstream any more. If this isn’t easily fixable we will just have to remove the feature. Not sure how many users this has.
>
> The last version is 2.99.4.5 (V3-beta) from 2015. I took a quick look
> and there are a *lot* of changes. Hm!
>
> Demo-Screenshots:
> https://cord.de/files/calamaris/calamaris-3/
> https://cord.de/files/calamaris/calamaris-3-frame/
This is the HTML report. I am not sure if our version could generate those, but text is obviously easier.
> But I don't know if I can handle this - looks complicated - and I'd like
> to make a possible update dependent on the number of seriously
> interested users.
Yeah, I suppose if a drop-in replacement works we can ship it. Otherwise it is not worth the effort. We have so many other things that are more important and more people would benefit from.
> Or I just send a patch with the above change.
Yes, please do.
>
> Anyone? Opinions?
>
> Best,
> Matthias
next parent reply other threads:[~2019-11-13 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18eb03fa-0045-4565-d889-e910c1ff4670@ipfire.org>
2019-11-13 16:58 ` Michael Tremer [this message]
2019-11-13 17:30 ` Matthias Fischer
2019-11-10 14:47 Matthias Fischer
2019-11-11 13:14 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AACA7F30-0889-4601-A799-9B59779604CF@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox