Am 18.02.2014 16:57, schrieb Peter Milesson: > On 2014-02-18 16:03, Reindl Harald wrote: >> >> Am 18.02.2014 15:54, schrieb Peter Milesson: >>> Found the culprit. It's gmime. Upgraded from gmime-2.4.15 to 2.6.15, and >>> the problems I have described started to >>> make themselves known. Now I have been tracking down which gmime version is >>> the last one not causing problems. >> >> from my expierience you can use the last recent >> see changelog below >> 2.6.12 drove me crazy by completly breaking dbmail >> >> [harry@rh:~]$ rpm -q --changelog gmime >> * Mo Okt 21 2013 Reindl Harald <[email protected]> >> - update to upstream 2.6.19 bugfix release >> >> * Mo Sep 16 2013 Reindl Harald <[email protected]> >> - update to upstream 2.6.18 bugfix release >> >> * Di Sep 03 2013 Reindl Harald <[email protected]> >> - update to upstream 2.6.17 bugfix release >> >> * Mi Aug 28 2013 Reindl Harald <[email protected]> >> - build own gmime-package because 2.6.12 from Fedora 18 breaks dbmail >> completly >> - Paul Stevens (dbmail-upstream) says he is using 2.6.10 >> - remove all the mono-crap and outdated packaging style from SPEC >> - remove docdir from devel-package >> - build gmime with "fstack-protector-strong" to catch memory violations >> >> * Fr Mai 18 2012 Richard Hughes <[email protected]> >> - Update to 2.6.9 > > Hi Harald, > > One of the problems is, that lots of libraries are distribution dependent. > Let's say gmime for Slackware is > definitely compiled with other parameters, than for the RedHat family. gmime > from 2.6.15 and up, did not even > compile under the version of Slackware I have been testing. I'm going to > recompile my last good known version > (2.6.9), and recompile DBMail 3.1.10 with that one. Cross my fingers :-)
that's why i started with the src.rpm of Fedora and removed first the mono-build-requirements and used the rest inclduing a fedora patch untouched, my tests clearly shown that there is no need to recompile dbmail for any gmime-2.6.x upgrade or downgrade in general i compile all my server packages at my own, adapt them, add some security params for the compiler and remove unused stuff they are simply replacing the distribution ones by raise the release-tag and so they are more or less identical while i decide the version and some minor details of the packaging without install stuff outside the systems package managment
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
