On Sunday 25 August 2013 19:18:33 Kingsley G. Morse Jr. wrote: > "The upgrade tries to migrate known configuration > files from /etc/apache2/conf.d/ to > /etc/apache2/conf-available/" > > I wonder if something went wrong with migrating my configuration file (...) Actually, "known" means supported by Debian, like built-in ones. For your information, apache2 will take care of these conffiles: /etc/apache2/conf.d/charset -> /etc/apache2/conf-available/charset.conf /etc/apache2/conf.d/localized-error-pages -> /etc/apache2/conf-available/localized-error-pages.conf /etc/apache2/conf.d/other-vhosts-access-log -> /etc/apache2/conf-available/other-vhosts-access-log.conf /etc/apache2/conf.d/security -> /etc/apache2/conf-available/security.conf And hopefully all packages will do the same for their own files. If you have home made configuration files, they are not "known" and *not* migrated automatically. I'm now merging this request with #710934.
Attachment:
signature.asc
Description: This is a digitally signed message part.