[pkg-bacula-devel] [pkg-bacula-commits] [bacula] 01/01: Enable automatic restarting of daemons with systemd (part 1)
sven at svenhartge.de
Sun Jul 17 19:03:45 UTC 2016
On 17.07.2016 16:42, Sven Hartge wrote:
> Last question left is: do we need Conflicts/Breaks if we move the init
> scripts or will the default dependencies be sufficient, allowing dpkg to
> do the right things in the correct order?
I just tested this on a Sid VM, upgrading from 7.4.2-1 to 7.4.2-3 (my
in-development packages) and this went fine, the init-script and service
files migrated ownership from bacula-director-common to
So the existing dependencies are fine, no need for special Conflicts/Breaks.
But: After a reboot the services would no longer start using the systemd
units, because /var/run/bacula was no longer existing, because
/etc/tmpfiles.d/bacula.conf is missing. It should be in bacula-common
but no longer ist.
ANd here I am totally confused. I looked at several of my systems, some
having the stock bacula-common_7.4.2-1 package which also does not
contain /etc/tmpfiles.d/bacula.conf but the systems *has* the file and
"dpkg -S /etc/tmpfiles.d/bacula.conf" tells me it is contained in
bacula-common but inspection the DEB clearly shows it is not there.
Have I hit a strange corner case with dpkg, where it thinks a file
belongs to a package if a former version provided the file but the file
then vanished from the package in a later version?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the pkg-bacula-devel