mod_http2 was backported from a newer version of apache2.
Grüße,
Sven Hartge.
signature.asc
Description: OpenPGP digital signature
On 10.02.19 14:36, Stefan Fritsch wrote:
> Between 2.4.25 and the fix for this issue, there were some intrusive
> changes in mpm_evnt. If we did a backport, rhe risk of introducing
> regressions would be quite high. Therefore, and because the next Debian
> stable release is quite near, I don't
On 11.02.19 10:29, Jan Wagner wrote:
> Am 11.02.19 um 09:51 schrieb Sven Hartge:
>> Also I am a bit disappointed by you invoking the "the next release is
>> near" argument. Most of my servers for example won't get Buster until
>> early to mid 2020 and I think
On 11.02.19 11:29, Jan Wagner wrote:
> Okay ... here is an area where you can push forward. What about
> providing documentation patches?
Sure. What kind of documentation. NEWS.Debian?
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
On 11.02.19 13:36, Jan Wagner wrote:
> Am 11.02.19 um 13:12 schrieb Sven Hartge:
>>> Okay ... here is an area where you can push forward. What about
>>> providing documentation patches?
>> Sure. What kind of documentation. NEWS.Debian?
> where would you expec
On 12.02.19 17:51, Gedalya wrote:
> On Mon, 11 Feb 2019 14:28:00 +0100 Sven Hartge wrote:
>>
>> Language of course needs a bit of refining from my German-English.
>>
>
>
> Nothing atrocious, really, but I was able to come up with something a bit
> more conci
On 10.03.19 12:51, Stefan Fritsch wrote:
> I am not comfortable with switching to mpm_worker, either, since this would
> be
> a significant behavior change.
>
> I have however tried a backport of the patch referenced in the upstream bug
> report and put a build here:
>
> https://people.debian
Um 08:56 Uhr am 11.03.19 schrieb Sven Hartge:
> I am going to test these package on the systems which have shown to be
> hit by regularly this problem here, so I am confident I will be able to
> report within two weeks if there have been any problems and if your
> change did in
On 22.03.19 21:14, Stefan Fritsch wrote:
> Second try with different approach is at
>
> https://people.debian.org/~sf/apache2-mpm-event-902493/2.4.25-3+deb9u7~test2/
>
> I have backported mpm_event from 2.4.28 and reverted one commit that was
> incompatible with 2.4.25. This was quite painless
On 22.03.19 21:19, Sven Hartge wrote:
> On 22.03.19 21:14, Stefan Fritsch wrote:
>
>> Second try with different approach is at
>>
>> https://people.debian.org/~sf/apache2-mpm-event-902493/2.4.25-3+deb9u7~test2/
>>
>> I have backported mpm_event from 2.4
On 24.03.19 02:02, Sven Hartge wrote:
> So far, so good. I have your packages running on the main webmail server
> and the main web server for my university and so far everything is fine,
> while default packages and the test1 packages with mpm_event would
> normally start showing
On 25.03.19 20:25, Sven Hartge wrote:
> On 24.03.19 02:02, Sven Hartge wrote:
>
>> So far, so good. I have your packages running on the main webmail server
>> and the main web server for my university and so far everything is fine,
>> while default packages and the test1
On 31.03.19 00:06, Sven Hartge wrote:
> On 25.03.19 20:25, Sven Hartge wrote:
>> On 24.03.19 02:02, Sven Hartge wrote:
>>
>>> So far, so good. I have your packages running on the main webmail server
>>> and the main web server for my university and so far ever
13 matches
Mail list logo
