On Oct 19, 2017, at 11:29 AM, Marius Schamschula wrote:
> However, I don’t see how this could have happened, as apache2 @2.4.28_2 was
> modified to not do this very thing, i.e. it moves the .conf files to
> .conf.orig in the post-destroot phase, before activation.
2.4.28.0_0 'owned' .conf files
Murray,
I’m sorry for that.
However, I don’t see how this could have happened, as apache2 @2.4.28_2 was
modified to not do this very thing, i.e. it moves the .conf files to .conf.orig
in the post-destroot phase, before activation.
I was debating, if backing up and littering numerous files in
About two days ago I went through the painful process of upgrading apache2 from
2.2 to 2.4. That involved a lot of manual moving of files and editing .conf
files, because of the radical changes of locations in 2.4 vs. 2.2.
Now today I upgraded apache2 from 2.4.28_0 to 2.4.28_2 and that DESTROYED
