Bug 12312 - correctly upgrade under Apache 2.2v3.16.00-pkg
commit25b10a2f3c35721fe300e88154278531447fef1a
authorRobin Sheat <robin@catalyst.net.nz>
Mon, 26 May 2014 01:28:00 +0000 (26 13:28 +1200)
committerGalen Charlton <gmc@esilibrary.com>
Mon, 26 May 2014 03:45:28 +0000 (26 03:45 +0000)
tree3380153c3d52191b92fe1f1d3aa52d25e7a4dd62
parent50078d04c6c3e3e85d6f8ed3645368f7a69402e5
Bug 12312 - correctly upgrade under Apache 2.2

As the way we need to reference Apache instance names has now changed
between 2.2 and 2.4, we need to try it out both ways to make sure we get
it right.

This also allows koha-create/koha-disable to try the .conf version of
the name if the first one doesn't work.

To test:
* Create an instance on an Apache 2.2 system with koha < 3.16
* Upgrade to 3.16 with this patch, saying 'yes' to the renaming question
** Make sure you don't see the warning: Warning: problem enabling $site
   in Apache
* Do a 'service apache2 restart'
* Make sure you can still access the instance
* Make sure that /etc/apache2/sites-enabled/instance.conf exists as a link
  to /etc/apache2/sites-available/instance.conf
* Check that koha-create and koha-remove behave like you'd expect.

Note:
* If you need to make debconf forget that it asked you the question
  about renaming so that it'll do it again, then run:
  echo "unregister koha-common/rename-apache-vhost-files" | sudo debconf-communicate koha-common
* 'debconf-show koha-common' will show you the current debconf
  configuration.

Signed-off-by: Galen Charlton <gmc@esilibrary.com>
debian/koha-common.postinst
debian/scripts/koha-create
debian/scripts/koha-remove