public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Apache Updates
Date: Tue, 05 Sep 2017 21:56:06 +0100	[thread overview]
Message-ID: <1504644966.3579.23.camel@ipfire.org> (raw)
In-Reply-To: <001801d325a1$f5455380$dfcffa80$@googlemail.com>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Hello,

I already merged v2 of the patchset. Unfortunately no comments have
been made publicly so I did not see any reason to hold back.

However, please send new patches that apply the changes described below
based on next for fast inclusion.

Best,
-Michael

On Mon, 2017-09-04 at 19:19 +0200, Wolfgang Apolinarski wrote:
> Hi everyone,
> 
> after Matthias Fischer was able to test the patches, I update them here again, only two small changes. Apparently, the tar process packs the whole directory, when a directory is in the rootfile. This is why the /usr/lib/apache and the /usr/lib/apr-util-1 directory are now commented out.
> 
> During an update, the following files should be deleted (thanks to Matthias for testing that):
> In /usr/lib/apache:
> mod_authn_default.so
> mod_authz_default.so
> mod_cern_meta.so
> mod_cgi.so
> mod_ident.so
> mod_imagemap.so
> 
> In /usr/sbin:
> htpasswd
> 
> The directory: /usr/lib/php/extensions/no-debug-non-zts-20090626/
> 
> In /usr/lib:
> libapr-1.so.0.5.1
> libapr-1.so
> libaprutil-1.so.0.5.3
> 
> In /usr/lib/apr-util-1:
> apr_dbd_sqlite3-1.so
> apr_dbd_sqlite3.so
> 
> Best regards,
> Wolfgang
> PS.: I support the latest discussions about updates for the configuration of apache, but it could make sense to first make the transition to Apache 2.4 and then apply them.
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-09-05 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 17:19 Wolfgang Apolinarski
2017-09-05 20:56 ` Michael Tremer [this message]

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=1504644966.3579.23.camel@ipfire.org \
    --to=michael.tremer@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