[pkg-bacula-devel] Bug#755089: bacula: purging one director package removes bacula-dir.conf of other director package

[Jan Niehusmann]

Source: bacula
Severity: important

In the following sequence of events, the file
/etc/bacula/bacula-dir.conf of the currently used
director got removed:

install bacula-director-sqlite3
replace bacula-director-sqlite3 with bacula-director-pgsql
happily use bacula for several years :-)
prune bacula-director-sqlite3
wonder why bacula doesn't work any longer...

The point is, purging one bacula-director-* package removes the config
file even if another bacula-director-* package is still installed and in
active use.

This, of course, can happen with other storage drivers.
The postrm scripts are all generated from the file
bacula-director-db.postrm.in, which unconditionally removes
/etc/bacula/bacula-dir.conf during purge.

It seems like the postrm script already handles other files properly
(/etc/default/bacula-dir, /etc/bacula/scripts/delete_catalog_backup).

I'm not assigning a 'grave' severity, because the data loss is limited,
and because the bacula docs say:

	Make a copy of your Bacula .conf files, particularly your
	bacula-dir.conf, and your bacula-sd.conf files, because if your
	server goes down, these files will be needed to get it back up
	and running, and they can be difficult to rebuild from memory.

Still, loss of bacula-dir.conf may be very inconvenient.

Regards,
Jan

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (990, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

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