Bug 40901: (QA follow-up) Migrate debconf answers from koha-common to koha-core

The debconf questions moved from the koha-common/* to the koha-core/*
namespace, but nothing carried the existing answers across, so a site
that had opted out of automatic translation updates was asked again
and defaulted back to "yes". koha-core.config now seeds the new
question, including its "seen" flag, from the old one when it exists.

debian/koha-common.templates was left behind after koha-common.config
was deleted; the metapackage registered three questions that no config
script ever asks, so remove it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Martin Renvoize <martin.renvoize@openfifth.co.uk>
Signed-off-by: Pedro Amorim <pedro.amorim@openfifth.co.uk>
This commit is contained in:
Martin Renvoize 2026-09-15 17:30:20 +01:00 committed by Pedro Amorim
parent 67d9b903d6
commit 2992ea058b
No known key found for this signature in database
GPG Key ID: 06B75BA7F3894D55
2 changed files with 10 additions and 25 deletions

View File

@ -1,25 +0,0 @@
Template: koha-common/3.2-3.4-upgrade-notice
Type: note
Description: koha-common upgrade actions required
If you are upgrading from a Koha 3.2 to 3.4 release, you must run:
sudo /usr/sbin/koha-upgrade-to-3.4
.
For large catalogues, running this may take a while. Your Koha installation
should be largely operational during the process, but some things,
particularly to do with items, may appear strange until the upgrade and
re-index is complete.
Template: koha-common/automatically-update-translations
Type: boolean
Default: true
Description: automatically update translations
When Koha is upgraded, any existing translated templates can be regenerated
to keep everything in sync. Select "yes" if you want this.
Template: koha-common/rename-apache-vhost-files
Type: boolean
Default: true
Description: Rename the Apache virtual hosts files for Koha instances?
When Koha is upgraded, the Apache's virtual host definition files can be
renamed to match the needs of the newer Apache 2.4. Previously defined
Koha instances will get their Apache files appended '.conf'.

View File

@ -23,6 +23,16 @@ set -e
CONFIGFILE=/etc/koha/koha-common.conf CONFIGFILE=/etc/koha/koha-common.conf
# Carry the answer (and its "seen" flag) over from the pre-split koha-common
# package so upgrading sites are not asked again. The value from
# $CONFIGFILE below still wins when the file exists.
if db_get koha-common/automatically-update-translations && [ -n "$RET" ]; then
db_set koha-core/automatically-update-translations "$RET"
if db_fget koha-common/automatically-update-translations seen && [ "$RET" = "true" ]; then
db_fset koha-core/automatically-update-translations seen true
fi
fi
if [ -e $CONFIGFILE ]; then if [ -e $CONFIGFILE ]; then
. $CONFIGFILE || true . $CONFIGFILE || true
# Put the current values into debconf # Put the current values into debconf