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

[jgoerzen]

Hi Jan,


   Thanks! that was it.  Disabling git patch in the gar build system and 
now the git-commit hash is correct.


regards,

Jake


On 08/31/2016 09:22 AM, Jan Holzhueter wrote:
> Hi,
> check how the version is generated.
>
> May guess would be it check if it's build from within a git repo.
> Since we initialize a new git for patching etc you will get a different
> hash every time. so either patch the version.sh or whatever they use to
> generate that string. Or try with NOGITPATCH += 1
>
> this will skip the git creation
>
> Greetings
> Jan
>
>
>
>
>
> Am 31.08.16 um 17:36 schrieb jgoerzen:
>> Hi Folks,
>>
>>
>>    I noticed that the commit hash is different for each architecture and
>> memory model even though they are all built with the same source and
>> configuration.  Not sure what is going on here.  Anyone have an idea?
>>
>>
>> Thanks,
>>
>> Jake
>>
>>
>> jgoerzen at unstable10x  > work/solaris10-i386/pkgroot/opt/csw/bin/doveconf -n
>> # 2.2.25 (da97823): /etc/opt/csw/dovecot/dovecot.conf
>> # OS: SunOS 5.10 i86pc
>>
>>
>> jgoerzen at unstable10x  >
>> work/solaris10-i386/pkgroot/opt/csw/bin/amd64/doveconf -n
>> # 2.2.25 (68082dc): /etc/opt/csw/dovecot/dovecot.conf
>> # OS: SunOS 5.10 i86pc
>>
>>
>> jgoerzen at unstable10s > work/solaris10-sparc/pkgroot/opt/csw/bin/doveconf -n
>> # 2.2.25 (1a99093): /etc/opt/csw/dovecot/dovecot.conf
>> # OS: SunOS 5.10 sun4v
>>
>>
>> jgoerzen at unstable10s  >
>> work/solaris10-sparc/pkgroot/opt/csw/bin/sparcv9/doveconf -n
>> # 2.2.25 (bbc8e6b): /etc/opt/csw/dovecot/dovecot.conf
>> # OS: SunOS 5.10 sun4v
>>
>>
>>
>>
>> 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