dovecot - Sep 2016 - 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

Hello Timo,

from the maintainer of the OpenCSW package I got the below answer.

As the newly build package yields another different commit hash (which I
cannot find on GitHub too), I would ask, if you are sure that the commit
hash-output in 'doveconf -n' is generated correctly?

The headline of 'doveconf -n' with the newly build package is
# 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf

Many thanks for your help,
Andreas

-------- Weitergeleitete Nachricht --------
Betreff: Re: OpenCSW question about package CSWdovecot
Datum: Tue, 30 Aug 2016 08:56:44 -0700
Von: jgoerzen <jgoerzen at opencsw.org>
An: piper at hrz.uni-marburg.de

Hello Andreas,


   The OpenCSW dovecot package was built using the 2.2.25 version
release tarball.  No code changes or patches have been applied. I'm not
sure what happened.  I will respin new packages and then check to see if
the git-commit hash is correct.  When the packages are done building
I'll put them in the experimental catalog:


http://buildfarm.opencsw.org/experimental.html#jgoerzen


Thanks,

Jake







On 08/29/2016 11:59 PM, piper at hrz.uni-marburg.de
wrote:
> Hello,
>
> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get
core-dumps as documented in my bug-report at the dovecot-mailing-list:
http://dovecot.org/list/dovecot/2016-August/105321.html
> In reaction to my bug-report, Timo Sirainen asks, which git-commit of the
dovecot-sources was used for this package:
http://dovecot.org/list/dovecot/2016-August/105332.html
>
> Could you shed some light on this?
>
> Thanks a lot,
> Andreas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5176 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20160831/2b393cf6/attachment-0001.p7s>

Hi Andreas & Timo,


   I've found out what is causing the incorrect hash in the built 
packages.  Our build system use here at OpenCSW has internal git 
patching capability.  I disabled it and rebuild again.  This time all 
architectures and memory model's are reporting the correct git-commit 
hash 7be1766.  Thank you Andreas for noticing and reporting this.


regards,

Jake


On 08/31/2016 06:17 AM, Piper Andreas wrote:
> Hello Timo,
>
> from the maintainer of the OpenCSW package I got the below answer.
>
> As the newly build package yields another different commit hash (which I
> cannot find on GitHub too), I would ask, if you are sure that the commit
> hash-output in 'doveconf -n' is generated correctly?
>
> The headline of 'doveconf -n' with the newly build package is
> # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf
>
> Many thanks for your help,
> Andreas
>
> -------- Weitergeleitete Nachricht --------
> Betreff: Re: OpenCSW question about package CSWdovecot
> Datum: Tue, 30 Aug 2016 08:56:44 -0700
> Von: jgoerzen <jgoerzen at opencsw.org>
> An: piper at hrz.uni-marburg.de
>
> Hello Andreas,
>
>
>     The OpenCSW dovecot package was built using the 2.2.25 version
> release tarball.  No code changes or patches have been applied. I'm not
> sure what happened.  I will respin new packages and then check to see if
> the git-commit hash is correct.  When the packages are done building
> I'll put them in the experimental catalog:
>
>
> http://buildfarm.opencsw.org/experimental.html#jgoerzen
>
>
> Thanks,
>
> Jake
>
>
>
>
>
>
>
> On 08/29/2016 11:59 PM, piper at hrz.uni-marburg.de wrote:
>> Hello,
>>
>> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes get
core-dumps as documented in my bug-report at the dovecot-mailing-list:
http://dovecot.org/list/dovecot/2016-August/105321.html
>> In reaction to my bug-report, Timo Sirainen asks, which git-commit of
the dovecot-sources was used for this package:
http://dovecot.org/list/dovecot/2016-August/105332.html
>>
>> Could you shed some light on this?
>>
>> Thanks a lot,
>> Andreas
>

Hi Jake,

thanks for fixing this. I have installed now the newly built package on
my production system and will report, if any more core dumps occur.

Regards,
Andreas

Am 31.08.2016 um 20:19 schrieb Jake Goerzen:
> Hi Andreas & Timo,
> 
> 
>   I've found out what is causing the incorrect hash in the built
> packages.  Our build system use here at OpenCSW has internal git
> patching capability.  I disabled it and rebuild again.  This time all
> architectures and memory model's are reporting the correct git-commit
> hash 7be1766.  Thank you Andreas for noticing and reporting this.
> 
> 
> regards,
> 
> Jake
> 
> 
> On 08/31/2016 06:17 AM, Piper Andreas wrote:
>> Hello Timo,
>>
>> from the maintainer of the OpenCSW package I got the below answer.
>>
>> As the newly build package yields another different commit hash (which
I
>> cannot find on GitHub too), I would ask, if you are sure that the
commit
>> hash-output in 'doveconf -n' is generated correctly?
>>
>> The headline of 'doveconf -n' with the newly build package is
>> # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf
>>
>> Many thanks for your help,
>> Andreas
>>
>> -------- Weitergeleitete Nachricht --------
>> Betreff: Re: OpenCSW question about package CSWdovecot
>> Datum: Tue, 30 Aug 2016 08:56:44 -0700
>> Von: jgoerzen <jgoerzen at opencsw.org>
>> An: piper at hrz.uni-marburg.de
>>
>> Hello Andreas,
>>
>>
>>     The OpenCSW dovecot package was built using the 2.2.25 version
>> release tarball.  No code changes or patches have been applied. I'm
not
>> sure what happened.  I will respin new packages and then check to see
if
>> the git-commit hash is correct.  When the packages are done building
>> I'll put them in the experimental catalog:
>>
>>
>> http://buildfarm.opencsw.org/experimental.html#jgoerzen
>>
>>
>> Thanks,
>>
>> Jake
>>
>>
>>
>>
>>
>>
>>
>> On 08/29/2016 11:59 PM, piper at hrz.uni-marburg.de wrote:
>>> Hello,
>>>
>>> with your newest dovecot-package 2.2.25,REV=2016.07.01, I sometimes
>>> get core-dumps as documented in my bug-report at the
>>> dovecot-mailing-list:
>>> http://dovecot.org/list/dovecot/2016-August/105321.html
>>> In reaction to my bug-report, Timo Sirainen asks, which git-commit
of
>>> the dovecot-sources was used for this package:
>>> http://dovecot.org/list/dovecot/2016-August/105332.html
>>>
>>> Could you shed some light on this?
>>>
>>> Thanks a lot,
>>> Andreas
>>
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5176 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20160901/bf1a39be/attachment.p7s>