[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Fwd: Re: Patch to update Exim to 18.104.22.168
On Thu, Apr 16, 2020 at 02:23:22PM +0100, Mike Pumford wrote:
> Oops. Wrong list :(
> -------- Forwarded Message --------
> Subject: Re: Patch to update Exim to 22.214.171.124
> 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:
> > 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.
> 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.
> The exim policy isn't actually to release these branches but provide
> bugfixes as git patches for package maintainers. Even the 126.96.36.199 release
> is an anomaly because of the really crazy bugs. Going to 188.8.131.52 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
shells/bash is an example of a package with a somewhat similar patch
policy. Hopefully it's similar enough that it can be done.
Main Index |
Thread Index |