[Pkg-puppet-devel] Bug#713070: puppetmaster-passenger: Fails to configure apache2 on wheezy

[Stig Sandbeck Mathisen]

Package: puppetmaster-passenger
Version: 3.2.2-1
Severity: serious
Justification: 6

This package installs on unstable, but have trouble installing on testing as
long as it does not have apache2.4.

This bug is filed by one of the maintainers to prevent migration to testing of
puppetmaster-passenger 3.2.2-1. (which is a bit sad, since that would fix a
security problem)

The problem lies with the "work on apache 2.4 AND apache 2.2" part of the
packaging:

 - The current package calls "a2ensite puppetmaster", while it sould call
   "a2ensite puppetmaster.conf" after configuration file rename (fixed in
   packaging VCS repository)

 - The package postinst creates /etc/apache2/sites-available/puppetmaster.conf
   (or puppetmaster), which confuses dpkg-maintscript-helper mv_conffiles,
   which again confused the maintainer for a while.

 - The symlink in /etc/apache2/sites-enabled could be renamed, but will still
   point to the wrong place.  Easier to use the apache2.4 (or 2.2) a2dissite
   and a2ensite after and before mv_conffiles on the vhost definition.

 - The vhost definition is not "installed by the package", it is "created by
   postinst".  This complicates matters, and seems to be the cause of
   mv_conffiles not being helpful.

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages puppetmaster-passenger depends on:
pn  libapache2-mod-passenger  <none>
ii  lsb-base                  4.1+Debian8+deb7u1
pn  puppetmaster-common       <none>
ii  ruby1.8                   1.8.7.358-7

puppetmaster-passenger recommends no packages.

puppetmaster-passenger suggests no packages.