On Sat, Jul 19, 2025 at 10:10:22AM +0200, Lucas Nussbaum wrote:
> The error is:
> > Preparing to unpack .../bacula-common_15.0.3-3_amd64.deb ...
> > dpkg: error processing archive
> > /var/cache/apt/archives/bacula-common_15.0.3-3_amd64.deb (--unpack):
> > new bacula-common package pre-installation script subprocess returned
> > error exit status 1
^^^^^^^^
> > systemd-tmpfiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not
> > found (required by /lib/x86_64-linux-gnu/libkmod.so.2)
>
> /var/lib/dpkg/info/bacula-common.postinst has:
^^^^^^^^
> > # Automatically added by dh_installtmpfiles/13.24.2
> > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
> > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
> > if [ -x "$(command -v systemd-tmpfiles)" ]; then
> > systemd-tmpfiles ${DPKG_ROOT:+--root="$DPKG_ROOT"} --create
> > bacula.conf || true
> > fi
> > fi
> > # End automatically added section
>
> I wonder if it would help to have bacula-common Depend on Pre-Depend on
> systemd to help apt decide to configure it before call systemd-tmpfiles
> in postinst.
>
The preinst script should be this:
https://binarycontrol.debian.net/cache/unstable/bacula-common/preinst
which does not invoke systemd-tmpfiles.
I wonder whats really happening. Is dpkg invoking the new postinst
(at postinst time), but putting "pre-installation" into the log message?
Or is it really invoking the postinst at preinst time?
Both look like a problem to me, and not something that Pre-Depends
should solve?
Best,
Chris
