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 <jgoer...@opencsw.org> An: pi...@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, pi...@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
smime.p7s
Description: S/MIME Cryptographic Signature
