Hi,
I'm seeing a similar issue trying to install build-deps.
Steps to reproduce:
Minimal system with build-essential installed running on a system that
does not have systemd installed
fakeroot fakechroot chroot ${buildchroot}
apt-get -y --only-source build-dep openssh=1:7.9p1-10+deb10u2
...
Setting up systemd (241-7~deb10u6) ...
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service ->
/lib/systemd/system/getty@.service.
Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target ->
/lib/systemd/system/remote-fs.target.
Created symlink /etc/systemd/system/dbus-org.freedesktop.timesync1.service ->
/lib/systemd/system/systemd-timesyncd.service.
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
-> /lib/systemd/system/systemd-timesyncd.service.
systemd-machine-id-setup: error while loading shared libraries:
libsystemd-shared-241.so: cannot open shared object file: No such file or
directory
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error
exit status 127
It can be resolved from _inside_ the chroot like this:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${buildchroot}/lib/systemd apt-get -y
--only-source build-dep openssh=1:7.9p1-10+deb10u2
Which, effectively, seems to be the same solution as was posted as a
proposed patch back in 2017. I've confirmed that the proposed patch also
fixes my issue.
This bug is tagged as fixed-upstream but I'm using 2.19-3.3 and the issue
is still present for me at least.
