Oops. Wrong list :( -------- Forwarded Message -------- Subject: Re: Patch to update Exim to 4.93.0.4 Date: Thu, 16 Apr 2020 14:02:20 +0100 From: Mike Pumford <mpumford%mudcovered.org.uk@localhost> CC: netbsd-users%netbsd.org@localhost <netbsd-users%netbsd.org@localhost> On 16/04/2020 12:32, Thomas Klausner wrote:
I can sympathise with that but without these patches exim can randomly crash or stop delivering mail due to really bad assumptions about how the heap allocator works and then tries to detect when those assumptions break. I can maintain them as local patches if necessary but exim from pkgsrc is going to be a risky proposition without them.On Thu, Apr 16, 2020 at 12:17:02PM +0100, Mike Pumford wrote:Looks like I need to pull more fixes from the 4.93+fixes branch upstream. How do I ensure that the patches get applied in a particular order as from the research I've done thats important.We don't want to maintain exim on a git level in pkgsrc - I suggest requesting a release from upstream.
The exim policy isn't actually to release these branches but provide bugfixes as git patches for package maintainers. Even the 4.93.0.4 release is an anomaly because of the really crazy bugs. Going to 4.93.0.4 has improved things but I'm still seeing random crashes or queue stalls. FreeBSD ports does have the patches (named alphabetically so that they are applied in order). I
That may not be possible without a LOT of extra work. I'm going to try a the patch series as local patches first and see what happens. They have to be applied in order as there are multiple patches that touch the same file.As for your question: if we add the patches in pkgsrc in the patches/ directory, they should be one-patch-per-source-file, so all modifications for one file combined into one patch.
Mike