The conf.d mechanism was revamped in the packaging for Apache 2.4. It's
now moved to conf-available, and the mechanisms for using these pieces
have substantially changed.
Thus, I think this bug is either fixed or superceded. If you think that
something still needs to be changed, then please
Some details of the new mechanism in 2.4 packaging is here:
https://wiki.debian.org/Apache/PackagingFor24
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in
