Package: backuppc
Severity: important
Version: 4.4.0-3
Installing backuppc initially on Bullseye, Bookworm or Sid (compared to
upgrading from Buster) on a system with init system which uses init
scripts (i.e. at least sysvinit-core and openrc) fails as follows:
Creating config file /etc/backuppc/config.pl with new version
Starting backuppc...BackupPC cannot be started because important parameters are
missing from config.pl.
If you just upgraded BackupPC, please update /etc/backuppc/config.pl.
invoke-rc.d: initscript backuppc, action "start" failed.
dpkg: error processing package backuppc (--configure):
installed backuppc package post-installation script subprocess returned error
exit status 1
Processing triggers for man-db (2.9.4-2) ...
Errors were encountered while processing:
backuppc
[#]
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up backuppc (4.4.0-3) ...
mkdir: cannot create directory '/var/lib/backuppc/pc/localhost/': File exists
dpkg: error processing package backuppc (--configure):
installed backuppc package post-installation script subprocess returned error
exit status 1
Errors were encountered while processing:
backuppc
Reason for the first error is the following outdated check in the init
script:
# Check for incompatible old config files
check_old_config()
{
BAD=0
CONF=/etc/backuppc/config.pl
grep -q IncrLevel $CONF || BAD=1
if [ "$BAD" = "1" ]; then
echo "BackupPC cannot be started because important parameters are
missing from config.pl."
echo "If you just upgraded BackupPC, please update
/etc/backuppc/config.pl."
exit 1
fi
}
But the upstream changelog says already for 3.1.0beta0 from 2007:
* $Conf{IncrLevels} is now defaulted if it is not defined.
It thouugh seems that the default config.pl got IncrLevels only removed
in one of the more recent upstream releases, so this never showed up
with the upstream release 3.3.2 which was in Debian before 4.4.0.
Reason for the second error is this line in the postinst script:
mkdir /var/lib/backuppc/pc/localhost/
It's obviously missing a "-p" option.
The "-p" is already fixed in git.
I intend the fix the initial error in git directly after sending
this bug report. Will upload to Debian Unstable soon afterwards.
And once the package migrated to testing, I intent to fix this as a
stable minor update for Bullseye as well. Sorry for any inconvenience
this might have caused. Definitely slipped through my testing.
Workaround for those who are affected:
* Call "rmdir /var/lib/backuppc/pc/localhost/",
* write "# Workaround: IncrLevel" somewhere on a single line into
config.pl,
* and then run "dpkg --configure --pending".
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'),
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1,
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
