On Oct 19, 2017, at 11:29 AM, Marius Schamschula <[email protected]> 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 - so they probably would have been removed when uninstalling for the upgrade. As of 2.4.28.0_2 the behavior is fixed (you can verify with 'port contents apache2) and so shouldn't cause future problems. -- Daniel J. Luke
