Mailing List Archive

dbmail-3.1.17 no longer builds on Fedora 32
besdies that a --disable-ssl option would be nice to avoid any linking
to openssl in case you have dovecot anyways in front dbmail-3.1.17 works
to build on F32 while the existing F31 binaries are still working :-(

/usr/bin/ld: .libs/libdbmail_la-dm_tls.o (symbol from plugin): in
function `tls_init':
(.text+0x0): multiple definition of `tls_context';
.libs/libdbmail_la-server.o (symbol from plugin):(.text+0x0): first
defined here
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:1888: libdbmail.la] Error 1
make[2]: *** [Makefile:2267: all-recursive] Error 1
make[1]: *** [Makefile:1705: all-recursive] Error 1
make: *** [Makefile:1634: all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.XHCeH4 (%build)

_______________________________________________
DBmail mailing list
DBmail@lists.nfg.nl
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
Am 19.08.2020 um 12:00 schrieb dbmail-request@lists.nfg.nl:
> Subject: [Dbmail] dbmail-3.1.17 no longer builds on Fedora 32
> Message-ID: <cecbd605-3001-ad46-375b-333fa53093a6@thelounge.net>
> Content-Type: text/plain; charset=utf-8
>
> besdies that a --disable-ssl option would be nice to avoid any linking
> to openssl in case you have dovecot anyways in front dbmail-3.1.17 works
> to build on F32 while the existing F31 binaries are still working :-(
>
> /usr/bin/ld: .libs/libdbmail_la-dm_tls.o (symbol from plugin): in
> function `tls_init':
> (.text+0x0): multiple definition of `tls_context';
> .libs/libdbmail_la-server.o (symbol from plugin):(.text+0x0): first
> defined here
> collect2: error: ld returned 1 exit status
> make[3]: *** [Makefile:1888: libdbmail.la] Error 1
> make[2]: *** [Makefile:2267: all-recursive] Error 1
> make[1]: *** [Makefile:1705: all-recursive] Error 1
> make: *** [Makefile:1634: all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.XHCeH4 (%build)
That's what I always have been worrying about in the last couple of years.
That at one point DBmail won't build anymore and my mail service got
sort of stuck...

Therefore switched to dovecot a few months ago and I'm actually not
looking back that much.

The switch from dbmail -> dovecot with imapsync went smooth and without
much hassle.
Ddovecot receives regular support & updates which makes me happy ;)

Still following the dbmail list but I think there won't be much progress
anymore?

Thanks & greetings
Becki

_______________________________________________
DBmail mailing list
DBmail@lists.nfg.nl
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
Am 21.08.20 um 17:08 schrieb Admin Beckspaced:
> Am 19.08.2020 um 12:00 schrieb dbmail-request@lists.nfg.nl:
>> Subject: [Dbmail] dbmail-3.1.17 no longer builds on Fedora 32
>> Message-ID: <cecbd605-3001-ad46-375b-333fa53093a6@thelounge.net>
>> Content-Type: text/plain; charset=utf-8
>>
>> besdies that a --disable-ssl option would be nice to avoid any linking
>> to openssl in case you have dovecot anyways in front dbmail-3.1.17 works
>> to build on F32 while the existing F31 binaries are still working :-(
>>
>> /usr/bin/ld: .libs/libdbmail_la-dm_tls.o (symbol from plugin): in
>> function `tls_init':
>> (.text+0x0): multiple definition of `tls_context';
>> .libs/libdbmail_la-server.o (symbol from plugin):(.text+0x0): first
>> defined here
>> collect2: error: ld returned 1 exit status
>> make[3]: *** [Makefile:1888: libdbmail.la] Error 1
>> make[2]: *** [Makefile:2267: all-recursive] Error 1
>> make[1]: *** [Makefile:1705: all-recursive] Error 1
>> make: *** [Makefile:1634: all] Error 2
>> error: Bad exit status from /var/tmp/rpm-tmp.XHCeH4 (%build)
> That's what I always have been worrying about in the last couple of years.
> That at one point DBmail won't build anymore and my mail service got
> sort of stuck...
>
> Therefore switched to dovecot a few months ago and I'm actually not
> looking back that much.
>
> The switch from dbmail -> dovecot with imapsync went smooth and without
> much hassle.
> Ddovecot receives regular support & updates which makes me happy ;)
>
> Still following the dbmail list but I think there won't be much progress
> anymore?

i can't simply switch easily to dovecot because a ton of automation
depends n the dbmail structure as well as backups of the whole database
server by shutdown a dedicated replication salve and rsync the whole
datadir to different locations is not possible that easy

FWIW:
%changelog
* Wed Aug 19 2020 Reindl Harald <h.reindl@thelounge.net>
- use '-fcommon' because of GCC10
(https://wiki.gentoo.org/wiki/Gcc_10_porting_notes/fno_common)
_______________________________________________
DBmail mailing list
DBmail@lists.nfg.nl
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
On 21/08/20 10:08, Admin Beckspaced wrote:
> Subject: [Dbmail] dbmail-3.1.17 no longer builds on Fedora 32
> Message-ID: <cecbd605-3001-ad46-375b-333fa53093a6@thelounge.net>
> Content-Type: text/plain; charset=utf-8
>
> besdies that a --disable-ssl option would be nice to avoid any linking
> to openssl in case you have dovecot anyways in front dbmail-3.1.17 works
> to build on F32 while the existing F31 binaries are still working :-(

3.1 is a very old development branch. Stable branch is 3.2.

Latest release is 3.2.5 https://github.com/dbmail/dbmail/releases/tag/v3.2.5

--
Sandino Araico Sánchez
http://sandino.net
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
Am 21.08.20 um 22:15 schrieb Sandino Araico Sánchez:
> On 21/08/20 10:08, Admin Beckspaced wrote:
>> Subject: [Dbmail] dbmail-3.1.17 no longer builds on Fedora 32
>> Message-ID: <cecbd605-3001-ad46-375b-333fa53093a6@thelounge.net>
>> Content-Type: text/plain; charset=utf-8
>>
>> besdies that a --disable-ssl option would be nice to avoid any linking
>> to openssl in case you have dovecot anyways in front dbmail-3.1.17 works
>> to build on F32 while the existing F31 binaries are still working :-(
>
> 3.1 is a very old development branch. Stable branch is 3.2.
>
> Latest release is 3.2.5 https://github.com/dbmail/dbmail/releases/tag/v3.2.5

tell me something new :-)

after the expierience with 3.0 and 3.1 which needed a ton of fast fixes
from Paul and the current prject inactivity update to 3.2 is not
schduled for now

there where a ton of "fun" from empty mails via POP3 over crashes of
lmtpd when a native autoreply got triggered to subtle reconstruct bugs
depending on imap clients while others prteneded it#s working just fine
both times

it's simply the wrong point of time to annoy endusers with email troubles
_______________________________________________
DBmail mailing list
DBmail@lists.nfg.nl
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
On 21/08/20 18:24, Reindl Harald wrote:
> tell me something new:-)
>
> after the expierience with 3.0 and 3.1 which needed a ton of fast fixes
> from Paul and the current prject inactivity update to 3.2 is not
> schduled for now
Project has been active on Github for some months.
>
> there where a ton of "fun" from empty mails via POP3 over crashes of
> lmtpd when a native autoreply got triggered to subtle reconstruct bugs
> depending on imap clients while others prteneded it#s working just fine
> both times

Those kind of issues could be expected in development branch.

Many stability issues have been fixed in 3.2 branch. It should be more
stable than any 3.1 release.

Depending on ehich 3.1 release you are, you might need to apply SQL
changes manually to the table structure. It might be helpful if you
compare the database schema with a newly installed one.

>
> it's simply the wrong point of time to annoy endusers with email troubles


--
Sandino Araico Sánchez
http://sandino.net
Re: dbmail-3.1.17 no longer builds on Fedora 32 [ In reply to ]
please don't reply-all on mailing-lists, thanks to the kill-dupes
feature of dbmail i get only one copy, but your offlist one is faster
and missing the list-headers

Am 22.08.20 um 02:09 schrieb Sandino Araico Sánchez:
> On 21/08/20 18:24, Reindl Harald wrote:
>> tell me something new :-)
>>
>> after the expierience with 3.0 and 3.1 which needed a ton of fast fixes
>> from Paul and the current prject inactivity update to 3.2 is not
>> schduled for now
> Project has been active on Github for some months.

still wrong point in time given the amount of other work

>> there where a ton of "fun" from empty mails via POP3 over crashes of
>> lmtpd when a native autoreply got triggered to subtle reconstruct bugs
>> depending on imap clients while others prteneded it#s working just fine
>> both times
>
> Those kind of issues could be expected in development branch.

i talk about the hundrets of ours to get 3.0 and 3.1 *final* releases
stable and stop the ongoing customer complaints about broken emails

> Many stability issues have been fixed in 3.2 branch. It should be more
> stable than any 3.1 release.

that was said about 3.1 back that time too :-)

> Depending on ehich 3.1 release you are, you might need to apply SQL
> changes manually to the table structure. It might be helpful if you
> compare the database schema with a newly installed one.

it might be helpful when the package contain migration sql-files

at least one sequence column i know about needs also taken care of in
the admin backends which have capabilities to move mails between folders
and users by update the dbmail database

>> it's simply the wrong point of time to annoy endusers with email troubles

anways, it's the wrong point in time, i have to stabilize major upgrades
of our platform which includes the dbmail backends and don't mix such
tasks with major upgrades

don't see dbmail 3.2.x in 2020 here
_______________________________________________
DBmail mailing list
DBmail@lists.nfg.nl
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail