upgrade apache2 2.4.28_0 < 2.4.28_2 destroyed .conf files!
lists at schamschula.com
Thu Oct 19 15:29:57 UTC 2017
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 /opt/local/etc/apache2/ was a better solution, but that way the user would have had to copy their backups back into place every time there was an update.
> On Oct 19, 2017, at 9:38 AM, Murray Eisenberg <murrayeisenberg at gmail.com> wrote:
> 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 all the careful customizations I had put into /opt/local/etc/apache2/
> including those in /opt/local/etc/apache2/extra/.
> For example, it wiped out all my customizations in /opt/local/etc/apache2/extra/httpd-vhosts.conf _without_ even the grace of saving the previous copies where I had made the customizations.
> This is unacceptable.
> (I did go into TimeMachine to restore all my customizations, but surely it should _NOT_ be necessary to backup all the config files oneself before upgrading apache2.)
> Please fix!
> Murray Eisenberg murrayeisenberg at gmail.com <mailto:murrayeisenberg at gmail.com>
> 503 King Farm Blvd #101 Home (240)-246-7240
> Rockville, MD 20850-6667 Mobile (413)-427-5334
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users