[Python-modules-team] Bug#836053: python-dbusmock: please invoke dbus-daemon directly, not dbus-launch

Simon McVittie smcv at debian.org
Tue Aug 30 10:22:28 UTC 2016


Source: python-dbusmock
Version: 0.16.6-1
Severity: normal
Tags: upstream
User: dbus at packages.debian.org
Usertags: dbus-launch dbus-launch-for-infra

As described in <https://lists.debian.org/debian-devel/2016/08/msg00554.html>
I'm trying to reduce how much dbus-launch is used in Debian.

This package currently has code that depends on dbus-x11 and explicitly
runs dbus-launch. I would prefer this to invoke dbus-daemon directly, similar
to this Flatpak commit:
https://github.com/flatpak/flatpak/commit/6cc8062cfb3f9410d54a27e7ccca77c103e441e8

If it would be more convenient, dbus-daemon can be asked to send both the
address and pid to stdout (--print-address=1 --print-pid=1). Their order
is undocumented but predictable, and I don't intend to break it in future
D-Bus releases.

After that has been done, the build-dependency and runtime dependency on
dbus-x11 can be changed to just dbus.

It would also be great if documentation that suggested wrapping tests in
dbus-launch was changed to suggest wrapping them in dbus-run-session(1),
which is better-designed for that mode of operation (the canonical
example is "dbus-run-session -- make check").

Thanks,
    S



More information about the Python-modules-team mailing list