[Pkg-utopia-maintainers] Bug#895261: RFS: dbus-broker/13-2 [ITP] -- Linux D-Bus Message Broker
daniele at grinta.net
Sat Jun 2 08:37:33 BST 2018
On 29/05/2018 11:39, Michael Biebl wrote:
> Am 29.05.2018 um 19:30 schrieb Daniele Nicolodi:
>> What would it take to have user services managed in a similar way as
>> system services? Should I look into implementing that in
>> init-system-helpers or should a new dh helper be created?
> It would need changes to both init-system-helpers and debhelper.
> Without having given this too much thought, I think we could add the
> missing functionality to dh_installsystemd and wouldn't need a
> completely new helper for this.
> If you are interested, there is
> and an older bug report
> Help on this would be really appreciated!
I started implementing support for systemd user instance units in
deb-systemd-helper. I would like to run the tests for that script, but
they currently fail also for a pristine checkout of init-system-helpers.
I see that the tests are run as autopkgtests, but with
TEST_ON_REAL_SYSTEM=1. However, running the tests like that is a bit
heavy, and not really convenient for development. Are the tests supposed
to run fin without that?
The first failure looks like this:
> (deb-systemd-helper DEBUG) is purge = no
> (deb-systemd-helper DEBUG) action = enable, scriptname = unit\x2dfSOUr.service, service_path = /lib/systemd/system/unit\x2dfSOUr.service
> (deb-systemd-helper DEBUG) Using systemctl preset to enable unit\x2dfSOUr.service
> /bin/systemctl: error while loading shared libraries: libsystemd-shared-238.so: cannot open shared object file: No such file or directory
> /home/daniele/src/init-system-helpers/t/../script/deb-systemd-helper: error: systemctl preset failed on unit\x2dfSOUr.service: No such file or directory
> not ok 14 - enable command succeeded
> # Failed test 'enable command succeeded'
> # at t/001-deb-systemd-helper.t line 100.
> # got: '256'
> # expected: '0'
'libsystemd-shared-238.so' is installed in /lib/systemd and it cannot be
found because the test harness bind mounts a temporary directory on that
path. It seems that no one has recently run the tests in that configuration.
More information about the Pkg-systemd-maintainers