Processed: Re: apache2: File conflict with libapache2-mod-proxy-uwsgi

Processing control commands: > found -1 2.4.33-2 Bug #894785 {Done: Stefan Fritsch } [apache2] apache2: File conflict with libapache2-mod-proxy-uwsgi Marked as found in versions apache2/2.4.33-2; no longer marked as fixed in versions apache2/2.4.33-2 and reopened. -- 894785:

Bug#894785: apache2: File conflict with libapache2-mod-proxy-uwsgi

Followup-For: Bug #894785 Control: found -1 2.4.33-2 Hi, the recently added Replaces: libapache2-mod-md (<< 2.4.33), libapache2-mod-proxy-uwsgi (<< 2.4.33) on apache2-bin misses a corresponding Breaks: libapache2-mod-md (<< 2.4.33), libapache2-mod-proxy-uwsgi (<< 2.4.33) otherwise partial

Bug#895237: apache2: apachectl does not use systemd for restarts

On Sunday, 15 April 2018 21:50:57 CEST Jan Heitkötter wrote: > The hooks in Let’s Encrypt’s conffile say “apachectl -k”; the manpage > does not explain this option. Omitting -k makes things work: options unknown to apachectl are passed to apache2 and apache2 -k start tells apache2 to do a normal

Bug#881725: apache2: reload fails inside (libvirt) lxc container

On Monday, 16 April 2018 21:51:36 CEST Stefan Fritsch wrote: > So tmpreaper should exclude systemd-private-* files by default. Moritz, do > you also have some cron job cleaning up stale files in /tmp ? tmpreaper needs to exclude dirs inside the systemd-private-* dir, too (there is a tmp dir