Hello Daniel
Please read apache2 debian news ( /usr/share/doc/apache2/NEWS.Debian.gz )
> Moreover, the configuration mechanism in Debian has changed. All
> configurations in sites-enabled and conf-enabled need a ".conf" suffix now.
This mechanism enable packages to deploy their configuration directly in
conf-available without symlinks, while NOT enabling .dpkg-new and similar
files by default. :)
Regarding the wiki, assuming you do not want to use dh_apache2,
I can read:
> Install the configuration file to
> /etc/apache2/conf-available/yourapplication.conf.
You do need a .conf extension.
Also, the wiki is quite explicit about the fact that you should use
"apache2_invoke enconf" and *not* a2enconf directly.
apache2_invoke enconf calls a2enconf with special flags like -m to enable
modules in maintainer mode. If you use a2enconf directly, and an administrator
then issue a2disconf, dpkg-reconfigure (or simple package upgrade) would
recreate the symlink in conf-enabled/, thus overiding the admin decision to
disable it, in violation of /etc preservation policy (RC bug).
Do use "apache2_invoke enconf" as described in the wiki pages.
You can use a symlink to another location such as /etc/loganalyzer/ if you so
prefer. The use of symlinks in conf-available is beyond the scope of apache2
help, IMHO. I don't know about any restriction about them regarding conf files.
On Tuesday 11 March 2014 15:32:05 Daniel Pocock wrote:
> Package: apache2
>
>
>
> My package fails piuparts with Apache 2.4:
>
> https://piuparts.debian.org/sid/fail/loganalyzer_3.6.5+dfsg-2.log
>
> Looking at that log, I notice:
>
> Setting up loganalyzer (3.6.5+dfsg-2) ...
> Module php5 already enabled
> Enabling module cgi.
> To activate the new configuration, you need to run:
> service apache2 restart
> ERROR: Conf loganalyzer does not exist!
>
>
> 0m37.5s ERROR: WARN: Broken symlinks:
> /etc/apache2/conf-available/loganalyzer -> /etc/loganalyzer/apache.conf
>
>
>
>
> So, it appears that
>
> a) the config file does exist, it is a symlink called
> /etc/apache2/conf-available/loganalyzer
>
> b) the command "a2enconf loganalyzer" fails
>
>
> Looking at some notes I found elsewhere, it appears that maybe my
> symlink should have a .conf extension or maybe it is not working at all
> because it is a symlink.
>
> The man page for a2enconf doesn't explain if a particular extension like
> .conf is needed and doesn't explain whether symlinks are supported
>
> This wiki also doesn't give exact details:
>
>https://wiki.debian.org/Apache/PackagingFor24
>
> Could you please clarify these things in the man page and the wiki?
>
>
>
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201403111717.55352.jmv_...@nirgal.com
