CppCheck Report Update

[Christian Lohmaier]

Hi Maarten, *,

On Thu, Jun 23, 2016 at 6:37 PM, Maarten Hoes <hoes.maarten at gmail.com> wrote:
> Hi,
>
>
> Ive taken the liberty of changing the crontab entry for the creation of the
> cppcheck report on vm140 from this :
>
> /home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
> /home/buildslave/source/libo-core -c /home/buildslave/source/cppcheck -w
> /home/buildslave/tmp/www >/tmp/cppcheck-report.log 2>&1
>
> to this :
>
> cd /home/buildslave/source/dev-tools && git pull &&
> /home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
> /home/buildslave/source/libo-core -c /home/buildslave/source/cppcheck -w
> /home/buildslave/tmp/www >/tmp/cppcheck-report.log 2>&1
>
> in order to make any future updates to the script automatically be used by
> means of a git pull of the corresponding dev-tools repo before running the
> script. Ive tested this on a local vm with the same Linux distro (Mageia 4),
> and it seems to work.
>
>
> By the way, searching through the mailing list archives it seems that the
> emails to the list reporting the success or failure of the
> cppcheck-report.sh run have stopped.
>
> Trying out the command (sendEmail) used (with the addition of '-vv') from
> the commandline on the vm, I get the following error :
>
>
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => Connecting to
> smtp.gmail.com:587
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => My IP address is:
> 89.238.68.140
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => evalSMTPresponse() - Found
> SMTP success code: 220
> Jun 23 17:49:30 vm140 sendEmail[2910]: SUCCESS => Received:     220
> smtp.gmail.com ESMTP x194sm4488242wmf.13 - gsmtp
> Jun 23 17:49:30 vm140 sendEmail[2910]: INFO => Sending:         EHLO
> vm140.documentfoundation.org
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => evalSMTPresponse() - Found
> SMTP success code: 250
> Jun 23 17:49:30 vm140 sendEmail[2910]: SUCCESS => Received:
> 250-smtp.gmail.com at your service, [89.238.68.140], 250-SIZE 35882577,
> 250-8BITMIME, 250-STARTTLS, 250-ENHANCEDSTATUSCODES, 250-PIPELINING,
> 250-CHUNKING, 250 SMTPUTF8
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => The remote SMTP server
> supports TLS :)
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => Starting TLS
> Jun 23 17:49:30 vm140 sendEmail[2910]: INFO => Sending:         STARTTLS
> Jun 23 17:49:30 vm140 sendEmail[2910]: DEBUG => evalSMTPresponse() - Found
> SMTP success code: 220
> Jun 23 17:49:30 vm140 sendEmail[2910]: SUCCESS => Received:     220 2.0.0
> Ready to start TLS
> Jun 23 17:49:30 vm140 sendEmail[2910]: ERROR => TLS setup failed: SSL
> connect attempt failed because of handshake problems error:1409442E:SSL
> routines:SSL3_READ_BYTES:tlsv1 alert protocol version
>
>
> I googled the (last line) error, and this page [1] seems to suggest to
> install different/better/more maintained/updated perl modules,

should  not be necessary - adjusting my $ssl_ver  to  TLSv1 should be enough;

I  took the liberty to change that :-)

ciao
Christian