Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-13 Thread Tony Meyer
> On 6/10/2015, at 2:52 am, Heiko Schlittermann wrote: > > The +fixes branch was invented to provide fast access to the most > important subset of changes without the need for new release. > > But you're right, if the urgency for (some of) the patches rises, we > should

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Arkadiusz Miśkiewicz
On Monday 05 of October 2015, Heiko Schlittermann wrote: > Yes, +fixes was the fastest possible way to distribute the important > fixes w/o starting a new release cycle and without forcing the > package/self-builders to backport/cherrypick the relevant patches by > themself. Too bad that this

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlittermann
Arkadiusz Miśkiewicz (Mo 05 Okt 2015 22:01:47 CEST): > On Monday 05 of October 2015, Heiko Schlittermann wrote: > > > Yes, +fixes was the fastest possible way to distribute the important > > fixes w/o starting a new release cycle and without forcing the > > package/self-builders

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlichting
Heiko Schlittermann wrote: > Arkadiusz Miskiewicz (So 04 Okt 2015 21:44:10 CEST): > > > > 4.87 (or 4.86.1) is really needed it seems :-/ > > Distro Maintainers are free to pick up the exim-4_86+fixes branch. Distro maintainers are free to use whatever they want but that does

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Jeremy Harris
On 05/10/15 11:06, Heiko Schlichting wrote: > Heiko Schlittermann wrote: >> Arkadiusz Miskiewicz (So 04 Okt 2015 21:44:10 CEST): >>> >>> 4.87 (or 4.86.1) is really needed it seems :-/ [...] >> 4.86. is reserved for security fixes. And a new 4.xx release would >> need more testing.

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Bjørnar Ness
2015-10-05 13:10 GMT+02:00 Heiko Schlichting : >> On 05/10/15 11:06, Heiko Schlichting wrote: >> > I strongly disagree. The lastest exim release should always usable and >> > stable. We had several releases in the past just correcting one or few >> > bugs (e.g. exim

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlichting
> On 05/10/15 11:06, Heiko Schlichting wrote: > > I strongly disagree. The lastest exim release should always usable and > > stable. We had several releases in the past just correcting one or few > > bugs (e.g. exim releases 4.84, 4.71, 4.66, 4.65). > > I'm not sure if you're disagreeing about

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlittermann
Heiko Schlichting (Mo 05 Okt 2015 12:06:22 CEST): > > 4.86. is reserved for security fixes. And a new 4.xx release would > > need more testing. … > Requiring the secret knowledge of undocumented git branches is not > supporting those of us which build exim from source

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlichting
Heiko Schlittermann wrote: > Heiko Schlichting (Mo 05 Okt 2015 12:06:22 CEST): > > > 4.86. is reserved for security fixes. And a new 4.xx release would > > > need more testing. > ... > > Requiring the secret knowledge of undocumented git branches is not > > supporting

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-05 Thread Heiko Schlittermann
Heiko Schlichting (Mo 05 Okt 2015 17:03:51 CEST): … > Uh, oh. Normally I follow the discussions but around the release of 4.86 my > newborn (second) son had blocked "some" ressources. I've totally missed the > existence of the +fixes branch. Congrats. Excuse accepted ;)

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-04 Thread Arkadiusz Miśkiewicz
On Saturday 03 of October 2015, Andreas Metzler wrote: > This sounds like which is > fixed in GIT head and GIT exim-4_86+fixes. 4.87 (or 4.86.1) is really needed it seems :-/ -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) -- ## List

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-04 Thread Bjørnar Ness
I feel that important fixes like this one should cause a prompt release... maby just me? -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-04 Thread Heiko Schlittermann
Arkadiusz Miśkiewicz (So 04 Okt 2015 21:44:10 CEST): > On Saturday 03 of October 2015, Andreas Metzler wrote: > > > This sounds like which is > > fixed in GIT head and GIT exim-4_86+fixes. > > 4.87 (or 4.86.1) is really needed it

[exim] Segfault in 4.86 (mail queue handleing)

2015-10-03 Thread Bjørnar Ness
I have seen this bug happening a few times in test now, and I do not exactly know how to reproduce, but I have seen references to it before as well, what I see is the following: 1) exim connects to remote mx to transport a message 2) When first message is sent, exim apparently searches its db for

Re: [exim] Segfault in 4.86 (mail queue handleing)

2015-10-03 Thread Andreas Metzler
Bjørnar Ness wrote: > I have seen this bug happening a few times in test now, and I do not > exactly know how to reproduce, but I have seen references to it > before as well, what I see is the following: > 1) exim connects to remote mx to transport a message > 2) When