Another thought... Could I use a different build mechanism that would result in
the same installation rpm? There's no reason I have to use source rpms,
I'm just used to it because of qmailtoaster.SteveSent from my T-Mobile 4G
LTE device------ Original message------From: steve at keptprivate.comDate: Thu,
Jan 7, 2021 3:48 PMTo: Aki Tuomi;dovecot at dovecot.org;Cc: Subject:Re: problem
building on centos 8 (8.3 kernel)
Any ideas about the lsb_release error in the spec file and where that came
from? I have a very vanilla centos 8 install I'm trying to bulid on. Any
thoughts appreciated because I'm stuck and at something of a loss on what to
try next. My first thought is to look at spec file revisions.SteveSent from my
T-Mobile 4G LTE device------ Original message------From: Aki TuomiDate: Thu, Jan
7, 2021 3:10 AMTo: steve at keptprivate.com;dovecot at dovecot.org;Cc:
Subject:Re: problem building on centos 8 (8.3 kernel)> On 07/01/2021 03:57
steve at keptprivate.com wrote:>
>
> Hi,
>
> I'm
converting from qmailtoaster/vpopmail build.> When I try to build dovecot-2.3.13-2.src.rpm for centos 8.3 the first thing
I run into is this:
>
> + sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh
doc/example-config/conf.d/10-ssl.conf
> + '[' -e buildinfo.commit ']'
> ++ head -1 buildinfo.commit
> + COMMIT=89f716dc2ec7362864a368d32533184b55fb7831
> ++ /bin/sh /home/build/rpmbuild/SOURCES/lsb_release -is
>
/bin/sh: /home/build/rpmbuild/SOURCES/lsb_release: No such file or
directory> + ID> error: Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
>
> RPM build errors:
> Macro expanded in comment on line 455: %{_libdir}/dovecot/settings
>
> Bad exit status from /var/tmp/rpm-tmp.WFaLYQ (%build)
>
> I can get past this with an edit to the dovecot.spec file (removing
sourcedir):
>
> if [ -e "buildinfo.commit" ]; then
> COMMIT=`head -1 buildinfo.commit`
> ID=`/bin/sh %?{?_?s?o?u?r?c?e?d?i?r?}?/?lsb_release -is`
> RELEASE=`/bin/sh
%?{?_?s?o?u?r?c?e?d?i?r?}?/?lsb_release -rs`> CODENAME=`/bin/sh %?{?_?s?o?u?r?c?e?d?i?r?}?/?lsb_release -cs`
> ARCH=`arch`
> fi
>
> The RPM builds but it fails to run with this message in the logs:
>
> Jan 6 20:52:11 beta1
systemd[1]: Starting Dovecot IMAP/POP3 email server...> Jan 6 20:52:11 beta1 systemd[1]: Started Dovecot IMAP/POP3 email server.
> Jan 6 20:52:11 beta1 dovecot[356909]: /usr/sbin/dovecot: error while
loading shared libraries: libdovecot.so.0: cannot open shared object
> file: No such file or directory
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Main process exited,
code=exited, status=127/n/a
> Jan 6 20:52:11 beta1 systemd[1]: dovecot.service: Failed with result
'exit-code'.
>
> Any ideas what I have going wrong?
>
> Also, a side question, when I build the rpm it's not running the
extensive tests that the old qmailtoaster source rpm used to run. I've
> looked through the spec file and I don't really see where to turn that
back on.
>
>
Sorry if any of this is stupid, but I'm new to building directly from the
dovecot repo.>
>
Steve
I think the file is installed under /usr/lib64/, so check
ldd /usr/lib64/libdovecot.so.0
Is there some reason you are building the rpms yourself?
Aki
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20210107/5f9259c5/attachment.html>