Koha-community/Koha - Koha - Koha: The world's first free and open source library system

Commit Graph

Author	SHA1	Message	Date
Tomás Cohen Arazi	b46e47840a	Bug 14106: (QA followup) avoid failures if no instances created If there are no instances already created on install/upgrade, the koha-common.postinst script hungs in the absence of files to fix and keeps waiting for user input. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>	9 years ago
Robin Sheat	48d793a0de	Bug 14106: patch existing zebra configs with new modulePath This patches the zebra configuration of existing Koha installations so that their modulePath will work on newer Debian (and presumably Ubuntu) releases. Testing: * Install a package built with this patch onto a system with instances created by an older Koha version. * Check that the files in /etc/koha/sites//zebra-.cfg have the new modulePath: directive rather than the old one. Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com>	9 years ago
Robin Sheat	1f5e92fec6	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>	10 years ago
Robin Sheat	2c5f927689	Bug 11404: (follow-up) only ask user if there are instances needing upgrading There's no point asking the user if they want their Apache Koha configuration updated if there's no configuration needing updated. This also fixes a case where the updating would have failed when running on Apache 2.4. Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com> I agree with adding that checks, and the conditions rewrite seems cleaner than my first approach. So, I sign it. Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Tomás Cohen Arazi	624c953b35	Bug 11404: Make the install process aware of the changes This patch makes the install scripts take care of the new file and prompt for user confirmation on the apache file renaming step. Both prompt and the renaming actions depend on the fact that there are instances with their files missing the .conf appendix. Sponsored-by: Universidad Nacional de Cordoba Signed-off-by: Robin Sheat <robin@catalyst.net.nz> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Tomás Cohen Arazi	2a7e71554b	Bug 10942: (QA followup) make warnings to to STDERR As noted by Robin, STDOUT is used by the script to communicate with debconf and, hence, the warning messages should be directed to STDERR. This patch does that. To test: - Set AUTOMATIC_TRANSLATIONS_UPDATE="no" so the warning normally shows - Redirect STDOUT to /dev/null: dpkg -i koha-common...deb > /dev/null => Warning message doesn't show (i.e. it is sent to STDOUT) - Apply the patch, rebuild package - Redirect STDOUT to /dev/null: dpkg -i koha-common...deb > /dev/null => Warning message shows (i.e. is correctly sent to STDERR) - Redirect STDERR to /dev/null: dpkg -i koha-common...deb 2> /dev/null => Warning message doesn't show - Verify that previous tests pass Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Robin Sheat	ee4e4917eb	Bug 10942: (follow-up) debconfing the update option This causes a question to be asked at installation time as to whether translations should be updated or not. The answer is written to the config file, and stored in debconf. Effort is taken to ensure that if the admin changes the config file, the update will be picked up and reflected in debconf (i.e. that the admin's decision is always the correct one.) Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com> Fixed two typos that made it fail and it worked like a charm. Tested like this: - Install the package => no errors, the file is created, defaults to 'yes' - Install a language (koha-translate --install es-ES) - Re-install the package (simulating an upgrade) => es-ES gets updated - Set preference to 'no' - Re-install => es-ES doesn't get updated, the warning is printed correctly - Installed a second language (koha-translate --install pt-BR) - did all the tests again => Success Note: on master there are obvious template translation warnings. A copy of the generated package can be grabbed from: http://es.koha-community.org/koha-common_3.15+20140312172225.af7c0a23_all.deb Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Galen Charlton	acd8a10251	Bug 10942: (follow-up) make AUTOMATIC_TRANSLATIONS_UPDATE default to yes This patch makes AUTOMATIC_TRANSLATIONS_UPDATE default to yes, meaning that package upgrades will update the translations by default. This seems definitely sensible for new installations, but as there are some older installations that may be in the habit directly editing generated translated templates, it's less clear whether this is a good idea for upgrades. This patch is intentionally separate, and can be ignored if the consensus swings towards having AUTOMATIC_TRANSLATIONS_UPDATE be off even for new installations or if somebody counter-patches with adding debconf support. To test: - As with the previous patches in the series, except that the translations would be automatically updated upon installing the new package. Signed-off-by: Galen Charlton <gmc@esilibrary.com> Signed-off-by: Robin Sheat <robin@catalyst.net.nz> Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Galen Charlton	83093abe89	Bug 10942: (follow-up) create a /etc/koha/koha-common.conf This patch creates a new master configuration file for the koha-common package, and moves the AUTOMATIC_TRANSLATIONS_UPDATE variable rather than leaving in in /etc/default/koha, which is meant to be used for init script settings. The configuration format is simple - a shell script that sets variables and which can sourced by another script or trivially parsed. To test: - Apply the patch series for bug 10942 and build a package. - Install the package. - Verify that a new config file, /etc/koha/koha-common.conf. - Follow the rest of the test plan for the main page (e.g., set AUTOMATIC_TRANSLATIONS_UPDATE and force a package upgrade). Signed-off-by: Galen Charlton <gmc@esilibrary.com> Signed-off-by: Robin Sheat <robin@catalyst.net.nz> Signed-off-by: Tomas Cohen Arazi <tomascohen@gmail.com> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	10 years ago
Tomás Cohen Arazi	33cc81bbc3	Bug 10942: Provide a way for package upgrades to update template translations This patch adds a new config variable AUTOMATIC_TRANSLATIONS_UPDATE at /etc/default/koha-common that is used to control whether the upgrade process should trigger a $ koha-translate --update <lang_code> command for each installed template translation language. To test: - Have a koha-common setup with some languages installed (e.g. koha-translate --install es-ES) - Apply the patch and build a package for it. - Install it. - A new AUTOMATIC_TRANSLATIONS_UPDATE config variable should be in place at /etc/default/koha-common - Set AUTOMATIC_TRANSLATIONS_UPDATE to 'yes' - Re-install the package to trigger the post-install script - Verify that translations get updated. Edit: added a warning message for the case AUTOMATIC_TRANSLATIONS_UPDATE=no and there are translations installed (so they need to get updated). Sponsored-by: Universidad Nacional de Cordoba Signed-off-by: Chris Cormack <chris@bigballofwax.co.nz> Works as advertised, default behaviour doesn't change. Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Robin Sheat <robin@catalyst.net.nz> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com> Signed-off-by: Galen Charlton <gmc@esilibrary.com>	11 years ago
Robin Sheat	c779f2b380	Bug 6361 - make the packages work with koha 3.4 This commit does the following: * Merge the changelog from the releases of 3.2 * Adds a command 'koha-upgrade-to-3.4' that does the MARC item splitting stuff. * Adds a debconf note to make sure people know that they need to run the above command. * Fixes the inclusion of jQuery in the packages. * Makes build-git-snapshot build packages with a 3.5 version. Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz>	13 years ago
Lars Wirzenius	5b12c69f27	Upgrade Koha instance database schema when package is upgraded. If the new version of Koha requires a newer version of the database schema, the Koha instances will work immediately after the package is upgraded, rather than after the sysadmin has run koha-upgrade-schema manually. Signed-off-by: Galen Charlton <gmcharlt@gmail.com>	14 years ago
Lars Wirzenius	f12ff9e0c6	Add support for a remote mysql server. Signed-off-by: Galen Charlton <gmcharlt@gmail.com>	14 years ago
Lars Wirzenius	d2985c6c92	Use /etc/mysql/koha-common.cnf instead of the Debian one. koha-common.postinst now creates a symlink to the Debian one. The sysadmin may replace that manually with something that allows Koha to access a remote mysql server. Signed-off-by: Galen Charlton <gmcharlt@gmail.com>	14 years ago
Lars Wirzenius	df6767467b	Add support for a remote mysql server. Signed-off-by: Galen Charlton <gmcharlt@gmail.com>	14 years ago
Lars Wirzenius	2ae1e3c21d	Use /etc/mysql/koha-common.cnf instead of the Debian one. koha-common.postinst now creates a symlink to the Debian one. The sysadmin may replace that manually with something that allows Koha to access a remote mysql server. Signed-off-by: Galen Charlton <gmcharlt@gmail.com>	14 years ago

14 Commits (fc66eedcc429e1eb8175d6e95bc5e921d8b94664)