From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apache: Update to 2.4.39
Date: Thu, 04 Apr 2019 15:06:00 +0000 [thread overview]
Message-ID: <f0867694-e5ff-b1a2-b766-2fdc21599bc7@ipfire.org> (raw)
In-Reply-To: <84E24F34-7BB9-45DC-B56A-1BD3E3AB1316@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]
Hello,
yes it is. :-)
@Matthias: Thanks for taking care of this.
Thanks, and best regards,
Peter Müller
Michael Tremer:
> Hi,
>
> Thanks for submitting this.
>
> Peter has emailed me in private that he wanted to update apache, but hasn’t sent a patch, yet.
>
> I guess that it is okay with him to merge this and save him the work.
>
> Best,
> -Michael
>
>> On 4 Apr 2019, at 08:15, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> For details see:
>> http://mirror.checkdomain.de/apache//httpd/CHANGES_2.4.39
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>> config/rootfiles/common/apache2 | 1 +
>> lfs/apache2 | 6 +++---
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/config/rootfiles/common/apache2 b/config/rootfiles/common/apache2
>> index ee09c6cbe..4866fb6bd 100644
>> --- a/config/rootfiles/common/apache2
>> +++ b/config/rootfiles/common/apache2
>> @@ -1646,6 +1646,7 @@ usr/lib/apache/mod_slotmem_plain.so
>> usr/lib/apache/mod_slotmem_shm.so
>> usr/lib/apache/mod_socache_dbm.so
>> usr/lib/apache/mod_socache_memcache.so
>> +usr/lib/apache/mod_socache_redis.so
>> usr/lib/apache/mod_socache_shmcb.so
>> usr/lib/apache/mod_speling.so
>> usr/lib/apache/mod_ssl.so
>> diff --git a/lfs/apache2 b/lfs/apache2
>> index be5ffd9ec..87f639efe 100644
>> --- a/lfs/apache2
>> +++ b/lfs/apache2
>> @@ -1,7 +1,7 @@
>> ###############################################################################
>> # #
>> # IPFire.org - A linux based firewall #
>> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
>> +# Copyright (C) 2007-2019 IPFire Team <info(a)ipfire.org> #
>> # #
>> # This program is free software: you can redistribute it and/or modify #
>> # it under the terms of the GNU General Public License as published by #
>> @@ -25,7 +25,7 @@
>>
>> include Config
>>
>> -VER = 2.4.38
>> +VER = 2.4.39
>>
>> THISAPP = httpd-$(VER)
>> DL_FILE = $(THISAPP).tar.bz2
>> @@ -45,7 +45,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_MD5 = 4a2b87ca55e42017d21f18724c560084
>> +$(DL_FILE)_MD5 = 930e217ba2d71e708a3f1521ecae7ec0
>>
>> install : $(TARGET)
>>
>> --
>> 2.18.0
>>
>
--
The road to Hades is easy to travel.
-- Bion of Borysthenes
next prev parent reply other threads:[~2019-04-04 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 7:15 Matthias Fischer
2019-04-04 10:07 ` Michael Tremer
2019-04-04 15:06 ` Peter Müller [this message]
2019-04-04 19:41 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0867694-e5ff-b1a2-b766-2fdc21599bc7@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox